←back to thread

264 points tosh | 10 comments | | HN request time: 0.229s | source | bottom
1. 0xblinq ◴[] No.44365314[source]
2025 and python packaging and dependencies management is still a mess.
replies(4): >>44365430 #>>44365736 #>>44367017 #>>44368247 #
2. incognito124 ◴[] No.44365430[source]
It's only a mess because not everyone has adopted uv yet (IMO)
replies(3): >>44365668 #>>44365728 #>>44370221 #
3. soulofmischief ◴[] No.44365668[source]
Python package management is a classic example of xkcd #927, and the community cannot be blamed for developing a Pavlovian response when it comes to yet-another-package-manager that promises to be the final solution.
4. greener_grass ◴[] No.44365728[source]
UV looks very promising but I can assure you, if everyone adopted it tomorrow we would see a long tail of scenarios that UV does not work well for.
replies(2): >>44367002 #>>44367341 #
5. ericfrederich ◴[] No.44365736[source]
Yes, it's a mess (New: now with Rust!)
6. bckr ◴[] No.44367002{3}[source]
I would love to see that happen and see how astral responds. I would love to see uv get built into Python 4
7. db48x ◴[] No.44367017[source]
Yep. The lesson is to get this right early in your language design. Do not punt until version 2.0. Think twice before putting the package/module/whatever metadata in an executable script. If you do decide to do that, think a third time. It works out better for some languages (like Common Lisp) than others (like Python).
8. tempest_ ◴[] No.44367341{3}[source]
I am perfectly content for a 90% solution, we should not let the perfect be the enemy of the good.
9. ikrenji ◴[] No.44368247[source]
never had a problem with dependencies. how is it a mess? you have requirements.txt and venv per project. doesn't get easier than that
10. 0xblinq ◴[] No.44370221[source]
It’s a mess because there’s no first party, properly thought out and working solution.

So every year we get a new “new way” to do it. Like that xkcd… this time this is the standard that will work!