@@ -98,6 +98,9 @@ email related to PEP administration (such as requesting a PEP number
98
98
or providing an updated version of a PEP for posting) should be sent to
99
99
this address (no cross-posting please).
100
100
101
+ The PEP editors watch the GitHub `PEP repository`_, so that's also a good way
102
+ to get in contact with them.
103
+
101
104
102
105
Submitting a PEP
103
106
----------------
@@ -136,11 +139,10 @@ python-ideas. This gives the author a chance to flesh out the draft
136
139
PEP to make properly formatted, of high quality, and to address
137
140
initial concerns about the proposal.
138
141
139
- Following a discussion on python-ideas, the proposal should be sent as a
140
- draft PEP to the PEP editors <
[email protected] >. The draft must be written
141
- in PEP style as described below, else it will be sent back without further
142
- regard until proper formatting rules are followed (although minor errors
143
- will be corrected by the editors).
142
+ Following a discussion on python-ideas, the proposal should be submitted as a
143
+ draft PEP via a `GitHub pull request`_. The draft must be written in PEP
144
+ style as described below, else it will fail review immediately (although minor
145
+ errors may be corrected by the editors).
144
146
145
147
If the PEP editors approve, they will assign the PEP a number, label it
146
148
as Standards Track, Informational, or Process, give it status "Draft",
@@ -549,8 +551,9 @@ Once the PEP is ready for the repository, a PEP editor will:
549
551
* Send email back to the PEP author with next steps (post to
550
552
python-list & -dev).
551
553
552
- Updates to existing PEPs also come in to
[email protected] . Many PEP
553
- authors are not Python committers yet, so PEP editors do the commits for them.
554
+ Updates to existing PEPs should be submitted as a `GitHub pull request`_.
555
+ Questions may of course still be sent to
[email protected] . Many PEP authors
556
+ are not Python committers yet, so PEP editors do the commits for them.
554
557
555
558
Many PEPs are written and maintained by developers with write access
556
559
to the Python codebase. The PEP editors monitor the python-checkins
@@ -605,6 +608,8 @@ References and Footnotes
605
608
606
609
.. _PEP repository: https://github.com/python/peps
607
610
611
+ .. _`GitHub pull request`: https://github.com/python/peps/pulls
612
+
608
613
609
614
Copyright
610
615
=========
0 commit comments