iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 609: Clarify expectations around PEP sponsors (#1425)

This commit is contained in:
Pradyun Gedam 2020-06-25 00:25:31 +00:00 committed by GitHub
parent a4a3b8f1dc
commit acffe50fdf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
pep-0609.rst
View File

@ -172,10 +172,11 @@ Python Steering Council has the final say in the acceptance of these
interoperability specifications. interoperability specifications.
It is expected (but not required) that the Python Steering Council It is expected (but not required) that the Python Steering Council
delegates the authority to approve or reject PEPs to individuals would delegate authority to sponsor and/or approve/reject PEPs related
within the PyPA community. At the time of writing (November 2019), the to packaging interoperability specifications, to individuals within the
Python Steering Council has `standing delegations`_ for currently PyPA community. At the time of writing (June 2020), the Python Steering
active packaging interoperability specifications. Council has `standing delegations`_ for currently active packaging
interoperability specifications.
The details of the process of proposing and updating the The details of the process of proposing and updating the
interoperability specifications are described in the `PyPA interoperability specifications are described in the `PyPA