clarifications
This commit is contained in:
parent
36087815b0
commit
8d042dd201
11
pep-0001.txt
11
pep-0001.txt
|
@ -324,15 +324,16 @@ of the PEP, it's probably best to send your comments and changes
|
|||
directly to the PEP author. For more mature, or finished PEPs you may
|
||||
want to submit corrections to the SourceForge `bug manager`_ or better
|
||||
yet, the SourceForge `patch manager`_ so that your changes don't get
|
||||
lost. If the PEP author is a SF developer, assign the bug/patch to
|
||||
him, otherwise assign it to the PEP editor.
|
||||
lost. If the PEP author is a SourceForge developer, assign the
|
||||
bug/patch to him, otherwise assign it to the PEP editor.
|
||||
|
||||
When in doubt about where to send your changes, please check first
|
||||
with the PEP author and/or PEP editor.
|
||||
|
||||
PEP authors who are also SF committers, can update the PEPs themselves
|
||||
by using "cvs commit" to commit their changes. Remember to also push
|
||||
the formatted PEP text out to the web by doing the following::
|
||||
PEP authors who are also Python/SourceForge committers can update the
|
||||
PEPs themselves by using "cvs commit" to commit their changes. PEP
|
||||
authors with python.org access should also remember to push the
|
||||
formatted PEP text out to the web by doing the following::
|
||||
|
||||
% python pep2html.py -i NUM
|
||||
|
||||
|
|
Loading…
Reference in New Issue