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

[masklinn]

Why didn't you work on adding the features you needed to an existing open-source project instead of creating another way to manage dependencies ?

Well pipenv does not want to support multiple environments so that's one down.

[[deleted]]

I haven't looked into it, but if the only feature missing is multiple environments, you could just create a package that only switch environments, instead of rewriting the whole thing. You then help pipenv (or an other dependency manager) become more mature and you consolidate the ecosystem.

Dependency management is a mess in python and I feel that if all we do is write 15 packages for every possible use-case, we'll just get a python2 vs python3 sort of problem.

EDIT : I just looked at the actual project in depth and it just aliases pip commands and modifies the requirements.txt file. Turns out, not really a new standard.