aboutsummaryrefslogtreecommitdiff
path: root/programming
diff options
context:
space:
mode:
authoralexpdp7 <alex@pdp7.net>2025-04-30 11:40:06 +0000
committeralexpdp7 <alex@corcoles.net>2025-04-30 13:40:43 +0200
commitb731fcc03d047a755ba533fecbc2f119f4f82bff (patch)
tree683205ff2bbc1359d4a75e96b1827d74f8e7c0a1 /programming
parent3be4f578d2a5ebd56296669ca13fd238a8980bbf (diff)
Retouch
Diffstat (limited to 'programming')
-rw-r--r--programming/python/dependency_handling.md7
1 files changed, 1 insertions, 6 deletions
diff --git a/programming/python/dependency_handling.md b/programming/python/dependency_handling.md
index 3f1db103..8acf0cee 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`