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
And I would like to ask the PPC to confirm that they will not accept such changes to the spec as GitHub issues on this repo, as it's not at all visible.
Agreed. Could you please post your proposal there @JacobCoffee?
And I would like to ask the PPC to confirm that they will not accept such changes to the spec as GitHub issues on this repo, as it's not at all visible.
Without speaking for the whole PPC as some kind of official statement right now, let me just confirm that (a) we have no intent of avoiding community review on any packaging spec changes, (b) we do want to help make that review process better, so will moderate and guide more as needed on Discourse, and (c) will be confirming/making decisions like these - easy if there's 100% consensus, but also still doable if there's some dissent.
This repo can be used to request decisions from the PPC, but not before community review for spec changes.
Please see bullets 3 and 4 about these topics in our meeting notes 28 Sep, which is roughly the longer version of what I said above.
The Packaging Council should consider setting up a procedure like at https://github.com/python/typing-council/, where spec changes require at least 1 week notice and a discussion on discuss.python.org first.
Activity
notatallshaw commentedon Oct 23, 2026
Please discuss first at https://discuss.python.org/c/packaging/14
And I would like to ask the PPC to confirm that they will not accept such changes to the spec as GitHub issues on this repo, as it's not at all visible.
pfmoore commentedon Oct 23, 2026
Agreed. I have some questions on this PR, but I'd like to discuss them in public on Discourse.
rgommers commentedon Oct 23, 2026
Agreed. Could you please post your proposal there @JacobCoffee?
Without speaking for the whole PPC as some kind of official statement right now, let me just confirm that (a) we have no intent of avoiding community review on any packaging spec changes, (b) we do want to help make that review process better, so will moderate and guide more as needed on Discourse, and (c) will be confirming/making decisions like these - easy if there's 100% consensus, but also still doable if there's some dissent.
This repo can be used to request decisions from the PPC, but not before community review for spec changes.
Please see bullets 3 and 4 about these topics in our meeting notes 28 Sep, which is roughly the longer version of what I said above.
Finally, it's also fine to drop by in the bi-weekly office hours we just started running, no appointment needed (see https://discuss.python.org/t/ppc-office-hours-for-2026-10-20/109575, still need to document that in this repo).
JelleZijlstra commentedon Oct 23, 2026
The Packaging Council should consider setting up a procedure like at https://github.com/python/typing-council/, where spec changes require at least 1 week notice and a discussion on discuss.python.org first.
JacobCoffee commentedon Oct 23, 2026
closing per DPO discussion - indexes can enact this via policy so I think its okay to no set a restriction for tools