4 ms·

Is managing deps in Python a pain? sure is!. Is it a pain in the other contenders of easily available dynamic languages? Yup. So that's a wash. Managing deps in

Is managing deps in Python a pain? sure is!. Is it a pain in the other contenders of easily available dynamic languages? Yup. So that's a wash. Managing deps in dynamic languages is not a simple problem, I can't say I've tried one that did it super well yet.

taeric 5y ago
I'm... Not sure insulting other languages is a path to victory. Npm, as much as it annoys me, is light-years ahead of anything in python. Quicklisp is rather pleasant, now. Ruby has had gems for a long time. I grant that it is a hard problem. I am not griping that it is not solved. More that the option community has largely failed to even pick a direction. The most used dependency methods are, in the modern spirit of python, deprecated already.
- iainctduncan 5y ago
  I'm not insulting other languages - I'm pointing out they have the same situation! Where in that post is there an insult??? I have had many dep fights with Ruby and Node too, and I would disagree that their solutions are in any way better than pip and virtualenv.
  - taeric 5y ago
    It isn't that similar. Most languages actually have solutions that the community are pushing together. Python alone bungled a major version change and then refused to endorse a package management system for so long.
- Tijdreiziger 5y ago
  > Npm, as much as it annoys me, is light-years ahead of anything in python. Hence PEP 582: > This PEP proposes to add to Python a mechanism to automatically recognize a __pypackages__ directory and prefer importing packages installed in this location over user or global site-packages. This will avoid the steps to create, activate or deactivate “virtual environments”. Python will use the __pypackages__ from the base directory of the script when present. https://peps.python.org/pep-0582/ https://peps.python.org/pep-0582/ I haven’t tried it yet, but there’s already a PEP 582-compatible dependency manager: PDM https://pdm.fming.dev/ https://pdm.fming.dev/
  - taeric 5y ago
    Right. I am confident they will get things in place to solve this. That it took so long for them to want to strengthens my assertion that the community was piggy backed on the machine package management for a lot of its initial popularity.

taeric 5y ago

I'm... Not sure insulting other languages is a path to victory. Npm, as much as it annoys me, is light-years ahead of anything in python. Quicklisp is rather pleasant, now. Ruby has had gems for a long time. I grant that it is a hard problem. I am not griping that it is not solved. More that the option community has largely failed to even pick a direction. The most used dependency methods are, in the modern spirit of python, deprecated already.

iainctduncan 5y ago
I'm not insulting other languages - I'm pointing out they have the same situation! Where in that post is there an insult??? I have had many dep fights with Ruby and Node too, and I would disagree that their solutions are in any way better than pip and virtualenv.
- taeric 5y ago
  It isn't that similar. Most languages actually have solutions that the community are pushing together. Python alone bungled a major version change and then refused to endorse a package management system for so long.
Tijdreiziger 5y ago
> Npm, as much as it annoys me, is light-years ahead of anything in python. Hence PEP 582: > This PEP proposes to add to Python a mechanism to automatically recognize a __pypackages__ directory and prefer importing packages installed in this location over user or global site-packages. This will avoid the steps to create, activate or deactivate “virtual environments”. Python will use the __pypackages__ from the base directory of the script when present. https://peps.python.org/pep-0582/ https://peps.python.org/pep-0582/ I haven’t tried it yet, but there’s already a PEP 582-compatible dependency manager: PDM https://pdm.fming.dev/ https://pdm.fming.dev/
- taeric 5y ago
  Right. I am confident they will get things in place to solve this. That it took so long for them to want to strengthens my assertion that the community was piggy backed on the machine package management for a lot of its initial popularity.