I've recently discovered pipenv, and it has been a massive QoL improvement. No need to figure out bazillion of commands just to create or start an environment, or deal with what params should you use for it like you do with venv. You just pipenv install -r requirements.txt, and everything is handled for you. And when you need to run it, just pipenv run python script.py and you are good to go.

The best thing however are the .pipfiles, that can be distributed instead of requirements.txt, and I don't get why it's not more common. It's basically requirements, but directly for pipenv, so you don't need to install anything and just pipenv run from the same folder.

[–] wyrmroot@programming.dev 2 points 1 year ago (1 children)

I could redraw this whole chart using only references to pipenv based on my experiences with managing it alongside other tools (especially homebrew). It’s good at many things but is no magic bullet.

[–] HarryEffingPotter@programming.dev 1 points 1 year ago* (last edited 1 year ago)

Yeah but is it really worse than python3-venv like some people act like it is? I just don't see it.

load more comments (2 replies)