3 ms·
The discussion here has quickly gotten out of hand and at the risk of causing more confusion I would like to point out that pipenv(http://docs.pipenv.org/en/lat
by abhirag 9y ago
The discussion here has quickly gotten out of hand and at the risk of causing more confusion I would like to point out that pipenv(http://docs.pipenv.org/en/latest/ http://docs.pipenv.org/en/latest/) seems to be the officially recommended Python packaging tool now[1], though venv and pip work too.
[1] -- (https://packaging.python.org/new-tutorials/installing-and-using-packages/ https://packaging.python.org/new-tutorials/installing-and-us...)
- smegel 9y agoWe are talking about packaging tools now?
- abhirag 9y agoKindly don't shoot the messenger(i.e. me) but pipenv does the work of pip + virtualenv + requirements.txt so packaging tool seems like a good name for it. Virtual environments aren't a lot of fun without local packages and reproducibility I assume.
- wink 9y agoLast time I tried pipenv (a month ago?) there was a breaking unresolved bug on Ubuntu 16.04. I'm not easy to hold grudges, but such a critical low-level tool manages to break for what I see as one of the most likely server environments to run on... I hold off on converting the (annoying, but working) virtualenv(wrapper) stuff. Just not worth it, now that I spent weeks of my life handling the annoyance that is python packaging and deployment.