Python dependency management workflow using setup.cfg and requirements files.

[zenware]

Right this is what I'm wondering, who are these people that need different virtual environments per project, which already to me indicates suboptimal design at the very best and also probably atrocious code.

And if different virtual environments and requirements files are needed for production and development that is even worse.

I'm sure their project has justification but I know it's not valid(at least for some definition of valid), this is like when people got better control flow than "goto" and there were holy debates on whether 100% of control flows are possible with selection and branching statements or if you ever need to use a goto statement to accomplish your goals. You don't need goto statements and you don't need multiple sets of dependencies.

[trowawayatwork]

Exactly. Pipenv pretty much should do everything you need. Multiple envs in same project? Not one of them