From b731fcc03d047a755ba533fecbc2f119f4f82bff Mon Sep 17 00:00:00 2001 From: alexpdp7 Date: Wed, 30 Apr 2025 11:40:06 +0000 Subject: [PATCH] Retouch --- programming/python/dependency_handling.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/programming/python/dependency_handling.md b/programming/python/dependency_handling.md index 3f1db10..8acf0ce 100644 --- a/programming/python/dependency_handling.md +++ b/programming/python/dependency_handling.md @@ -30,12 +30,7 @@ The constraint does not be an exact version, it can also be a range of versions, (Constraints additionally can specify other restrictions, such as requiring different versions for different Python versions, and other interesting possibilities.) -When using setuptools and dependencies using setuptools, you quickly can run into problems. - -If packages specify exact dependency versions, then there are many changes of packages having conflicting requirements. - -If packages do not specify exact dependency versions, then the actual versions that pip installs can vary as new versions of packages are released. -This can lead to bugs, because code might not work properly when using newer versions of dependencies. +In my opinion, although you can package applications and libraries properly using Setuptools, doing it correctly requires much knowledge, effort, and is error-prone. ## Version locking and `requirements.txt` -- 2.47.3