packaging.python.org
packaging.python.org copied to clipboard
pypa
Add tools comparison tables
Is it something that would be interesting for the guide in principle?
Preview:
- https://python-packaging-user-guide--1196.org.readthedocs.build/en/1196/discussions/packaging-tools-comparisons/
- https://github.com/sinoroc/packaging.python.org/blob/tools-comparison-tables/source/discussions/packaging-tools-comparisons.rst
Plan is to add more tools, most notably conda and maybe also things like Spack, scikit-build, and so on. But first I would like to have an agreement that something like this is useful, and that this form is suitable.
This PR looks really useful, but unfortunately has been open since January. Would any maintainer have the time to take a look?
@sinoroc If you fix the conflict, I would be happy to review. @jeanas If you want to give this an initial review, that would be great too.
@willingc, rebased.
For info:
- this initially took inspiration from Chris Warrick's "How to improve Python packaging, or why fourteen tools are at least twelve too many"
- since then PyOpenSci's Python packaging guide was created (or at least I found out about it after I started this PR)
- and also Anna-Lena Popkes' "An unbiased evaluation of environment management and packaging tools"
I do not know which form is the most appropriate.
I do not believe our guide should go too much into details in order to avoid risking being seen as choosing one tool over another (not the Pipenv story again). Also the more details we add, the more we have to keep everything up-to-date as those tools' scopes and feature sets evolve over time.
For sure what this needs is links (but those can be added at the end, because I find it quite annoying to do links in reStructuredText).
This also needs conda for sure, probably spack and maybe a bunch of other things (pex, shiv, pyinstaller, pyoxidize, and so on?). But hard to know what is the right balance. Maybe we do not want to have things that are too niche.
Thanks for the rebase @sinoroc. I think that it would be helpful to add a date to give the reader when the last time this was updated and note that tools are evolving so do check their documentation as well.