2 ms·
In case the author sees this: > Believe it or not, this is basically how everything in the Python and Ruby worlds work And those 2 paragraphs are not really t
by viraptor 4y ago
In case the author sees this:
> Believe it or not, this is basically how everything in the Python and Ruby worlds work
And those 2 paragraphs are not really true. Python and ruby environments don't exist "these days" - they've been available longer than npm existed. (virtualenv 2007, npm 2010)
The system/project split exists in the same way npm --global / npm exists. The only real difference is that you can't have different versions installed in the same environment at the same time - not the other things implied by the post.
- Aeolun 4y agoThe big problem for me is that python does not seem to have settled on just a single (or even obvious) way of dealing with this. Every project I have to figure out if I need to run setuptools, pip, virtualenv, etc. That said, I did have issues with the same paragraph, because php’s composer has been doing it the correct way since forever.
- viraptor 4y ago> Every project I have to figure out if I need to run setuptools, pip, virtualenv, etc. You're mixing layers. Pip uses setuptools to install packages inside a virtualenv. You need something that manages environment/dependencies and something that installs them. Sometimes they're the same thing, like with poetry or pipenv. How do you know what to use? Read the project readme. Same as people choosing yarn or npm.
- Aeolun 4y ago> How do you know what to use? Read the project readme. Same as people choosing yarn or npm. Actually no. If a repository has a package.json file I can run any package manager I want and it’ll work.