4 ms·
But this is exactly what virtualenv does... 1. You create a virtualenv 2. You enter the virtualenv 3. You install dependencies in it Redo these steps for ever
by Galanwe 11y ago
But this is exactly what virtualenv does...
1. You create a virtualenv
2. You enter the virtualenv
3. You install dependencies in it
Redo these steps for every isolated set of dependencies you want.
The solution proposed here does not solve anything. It only provides some half-working equivalent of virtualenv that works with a hidden directory to run your scripts...
- pyre 11y agoThe differences: 1. Your 'node_modules' is automatically created by npm. No need for a separate tool. 2. You don't have to 'enter' an npm environment other than changing to the directory where it exists. These really aren't huge issues, but I can see it being an annoyance for some, especially people coming from Node.js to Python.
- reverius42 11y agoThere is a more fundamental difference, which is what happens in a single project with a diamond-shape dependency with version mismatches, like this: A -> B, C B -> D == 0.1 C -> D == 0.2 This dependency graph is handled easily by npm and other tools (at the expense of disk space, memory usage, etc.) and potentially small incompatibilities/gotchas, but is completely impossible to satisfy with pip.