5 ms·

True. This same tutorial cites pip-tools, hatch, poetry. Does that mean that they “endorse” these tools as well?

• shakna 7y ago
  However, 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 ago
    Right, I stand corrected.
    • domoritz 7y ago
      So 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 ago
        It 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.