You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been discussing the need for updates to the Packaging Guide with the new Python Packaging Council (PPC) (xref python/packaging-council#8). There is a lot of outdated content; adding new content or reshuffling things will be easier once the very outdated stuff is removed. This issue is meant to communicate that plan, and discuss some rough criteria for what can be removed without needing more than two pairs of eyes. A proposal:
In general, everything that is (a) out of date by >3 years, or (b) no longer relevant or maintained can be removed. Examples:
The page install_requires vs requirements files is probably also outdated enough to remove - none of that is standardized or recommended, and it predates pyproject.toml introduction (now 10 years ago)
gh-2165 added a new 404 page, so that pages redirect to the front page (without that, the 404 shown was quite uninformative). Of course if there's a specific replacement for removed content, adding a redirect can be the better option.
The page install_requires vs requirements files is probably also outdated enough to remove - none of that is standardized or recommended, and it predates pyproject.toml introduction (now 10 years ago)
I often refer people to this page for the "abstract vs. concrete dependencies" paragraph. It works quite well for me as a mental model and it seems to have been successful at getting the message across. I think it would be good if this bit could be preserved somehow.
@sinoroc that's a very useful concept to explain, but this page does a pretty poor job of it. We can aim to write a better explanation in the packaging guide, but in the meantime, here are better alternatives for this page:
Activity
sinoroc commentedon Oct 27, 2026
I often refer people to this page for the "abstract vs. concrete dependencies" paragraph. It works quite well for me as a mental model and it seems to have been successful at getting the message across. I think it would be good if this bit could be preserved somehow.
rgommers commentedon Oct 28, 2026
@sinoroc that's a very useful concept to explain, but this page does a pretty poor job of it. We can aim to write a better explanation in the packaging guide, but in the meantime, here are better alternatives for this page: