5 ms·
> The python packaging team was officially recommending it NO! This is a common misconception[1]. Edit: Correction it's not endorsed by the core Python team b
by noname120 7y ago
> The python packaging team was officially recommending it
NO! This is a common misconception[1].
Edit: Correction it's not endorsed by the core Python team but it's recommended by the Python Packaging Authority in various places. See replies below for more info.
[1] https://chriswarrick.com/blog/2018/07/17/pipenv-promises-a-lot-delivers-very-little/#officially-recommended-tool-or-how-we-got-here https://chriswarrick.com/blog/2018/07/17/pipenv-promises-a-l...
- jplayer01 7y agoLook, if you can’t trust the endorsement of the organization that otherwise develops and maintains all of Python’s official packaging tools, who are you supposed to trust? Guido and only Guido? > The thing that made it “official” was a short tutorial [1] on packaging.python.org, which is the PyPA’s packaging user guide. Also of note is the Python.org domain used. It makes it sound as if Pipenv was endorsed by the Python core team. PyPA (Python Packaging Authority) is a separate organization — they are responsible for the packaging parts (including pypi.org, setuptools, pip, wheel, virtualenv, etc.) of Python
- noname120 7y agoTrue. This same tutorial cites pip-tools, hatch, poetry. Does that mean that they “endorse” these tools as well?
- shakna 7y agoHowever, over here [0] I see pipenv, but not those: > Use Pipenv to manage library dependencies when developing Python applications. See Managing Application Dependencies for more details on using pipenv. > Consider other tools such as pip when pipenv does not meet your use case. That recommendation is absolutely unambiguous. [0] https://packaging.python.org/guides/tool-recommendations/ https://packaging.python.org/guides/tool-recommendations/
- noname120 7y agoRight, I stand corrected.
- domoritz 7y agoSo if it isn't supposed to be officially endorsed, should someone file an issue at https://github.com/pypa/packaging.python.org/issues https://github.com/pypa/packaging.python.org/issues?
- shakna 7y agoIt hasn't been removed, because PyPA disagree [0]. > It's an official project of PyPA still, it's just not being pushed as the "be-all-end-all" option. [0] https://github.com/pypa/packaging.python.org/issues/589 https://github.com/pypa/packaging.python.org/issues/589
- doublement 7y ago> This same tutorial cites pip-tools, hatch, poetry. Does that mean that they “endorse” these tools as well? Those tools are relegated to a small section at the end, whereas the main body of the text says "Pipenv is recommended for collaborative projects..." I'd say that counts as a specific endorsement of Pipenv. I guess it's an endorsement by the "Python Packaging Authority" rather than "Python Core" but it's pretty hard for someone at the tutorial-reading level to perceive the difference.
- deleted 7y ago[deleted]
- jarnagin 7y agoIt’s officially recommended on packaging.python.org [1]. If that’s not enough to count as an official endorsement, what is? [1] https://packaging.python.org/guides/tool-recommendations/ https://packaging.python.org/guides/tool-recommendations/
- jzl 7y agoThose pages are managed by the "PyPA" group, not technically python.org itself, although they were given a subdomain there. Start here and follow the links for more info: https://hynek.me/articles/python-app-deps-2018/ https://hynek.me/articles/python-app-deps-2018/