3 ms·
1. Because pipenv is easier to use. 2. Because it's not at all clear that pipenv is a third party library. It's made by the same group that makes pip, so it's
by rthomas6 7y ago
1. Because pipenv is easier to use.
2. Because it's not at all clear that pipenv is a third party library. It's made by the same group that makes pip, so it's confusing that pip would be considered a de-facto standard but not pipenv when it's made by the same group, and under the same project in Github.
- blondin 7y agopip is not yet in the standard library. as opposed to venv.
- rthomas6 7y agoYes. And that is confusing, as pip is a de facto standard IMO.
- shakna 7y agoWhilst you might have to define "in the standard library", pip is added in PEP 453 [0] (accepted in 2013), in a similar capacity to venv: > However, to avoid recommending a tool that CPython does not provide, it is further proposed that the pip [18] package manager be made available by default when installing CPython 3.4 or later and when creating virtual environments using the standard library's venv module via the pyvenv command line utility. [0] https://www.python.org/dev/peps/pep-0453/ https://www.python.org/dev/peps/pep-0453/