2 ms·
Most projects don't need either. I only use pipenv on a work project with a hundred dependencies, and venv on one other large side project. Everything else is
by mixmastamyk 7y ago
Most projects don't need either.
I only use pipenv on a work project with a hundred dependencies, and venv on one other large side project. Everything else is installed with --user, especially dev tools like black and pyflakes. The user folder gets cleaned up every few years when you upgrade to a new version of python (rm ~/.local/lib/python3.5).
Has worked fine for a decade or two, no conflicts. I think some folks get spooked at python packaging and overcompensate in response, but it's pretty easy to troubleshoot when you've learned how it works.
- pbecotte 7y agoThis is only true in the limited case where you never have to share your code with anyone. If you want to share it, setting it up so others can get going without having to figure out which packages are missing is necessary. In that case, you should probably use that same tool yourself to make sure that your environment works the same as you expect others to use it.
- mixmastamyk 7y agoNope, share code all the time. That is what requirements.txt (and alternatives) are for. Where they install them is up to them.