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

Clarification on when and how to report PEP bugs and updates.

This commit is contained in:
Barry Warsaw 2001-08-14 22:48:14 +00:00
parent 03cbc71719
commit 3d503a4ea4
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
pep-0001.txt
View File

@ -279,9 +279,19 @@ PEP Style
Reporting PEP Bugs, or Submitting PEP Updates Reporting PEP Bugs, or Submitting PEP Updates
Please use the SourceForge bug manager[6] if you want to report How you report a bug, or submit a PEP update depends on several
problems with PEPs, or better yet, the SourceForge patch factors, such as the maturity of the PEP, the preferences of the
manager[2] for submitting patches to PEPs. PEP author, and the nature of your comments. For the early draft
stages 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[6] or better yet, the SourceForge patch manager[2] 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.
When in doubt about where to send your changes, please check first
with the PEP author and/or PEP editor.
References and Footnotes References and Footnotes