3 ms·
> Nor do we want to learn about how to build and maintain Python virtual environments This is a shame, because this is one thing that Python gets mostly right.
by skywhopper 6y ago
> Nor do we want to learn about how to build and maintain Python virtual environments
This is a shame, because this is one thing that Python gets mostly right. You don't have to fuss around with the shell wrapper, etc. For 90% of cases you can probably do:
$ virtualenv subdir-name
$ subdir-name/bin/pip install <package-names>
$ subdir-name/bin/python your-python-script.py
- inshadows 6y agoYou also lose tested versions from OS. You will either have to do your own QA of working dependency versions and manually keep them updated over time (e.g. security fixes, or stick with what you freeze forever), or just get dump of last versions every time you deploy the virtualenv.
- jnwatson 6y agoEach package owner probably knows much better about the dependencies than the "OS". Save for a handful of Python packages that have extra-Python OS dependencies, relying upon the explicit versions called out by the package owner is generally more reliable.
- pseudalopex 6y agoCreate the environment with --system-site-packages if you want the system packages.