Pipenv: promises a lot, delivers very little
I was sorely disappointed with pipenv, and transitioned to poetry [1], with which I’ve been very satisfied. There is also some commentary in the README on the design decisions re: pipenv [3]. Contrary to the author's perspective on poetry using poetry-specific sections of pyproject.toml, that's actually the proper implementation (and expected usage) coming out of PEP-518.<p>I also am a big fan of pyenv [3] but that’s of course to manage Python versions (not environments)<p>[1] <a href="https://github.com/sdispater/poetry" rel="nofollow">https://github.com/sdispater/poetry</a><p>[2] <a href="https://github.com/sdispater/poetry#what-about-pipenv" rel="nofollow">https://github.com/sdispater/poetry#what-about-pipenv</a><p>[3] <a href="https://github.com/pyenv/pyenv" rel="nofollow">https://github.com/pyenv/pyenv</a>