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
A concrete proposal for implementing this, roughly based on the concensus in the aforementioned thread, is:
Add an optional Track header for PEPs, that can have only one value for the initial implementation: Packaging.
Add this header to existing Python Packaging PEPs.
Add a track-specific index page, that lists all PEPs with that track: peps.python.org/track/packaging
This page should have a different header and introduction section than PEP 0.
The Track header can be expanded to other values in the future (Typing and Release are examples of proposed ideas from the aforementioned thread).
Personally, I think it's valuable to implement this for just Packaging as an initial pass since it's a viable "minimum" implementation of this mechanism and... perhaps more importantly... avoids an extended discussion on what these other values should be allowed/updated for. :)
CAM-Gerlach
changed the title
A concrete proposal for implementing this, roughly based on the concensus in the aforementioned thread, is:
Spam
Oct 15, 2022
Track
header for PEPs, that can have only one value for the initial implementation:Packaging
.peps.python.org/track/packaging
The Track header can be expanded to other values in the future (
Typing
andRelease
are examples of proposed ideas from the aforementioned thread).Personally, I think it's valuable to implement this for just Packaging as an initial pass since it's a viable "minimum" implementation of this mechanism and... perhaps more importantly... avoids an extended discussion on what these other values should be allowed/updated for. :)
Originally posted by @pradyunsg in #2572 (comment)
#2836 (comment)
The text was updated successfully, but these errors were encountered: