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

Make this a little bit less hilariously out of date.

This commit is contained in:
Michael W. Hudson 2004-05-26 16:10:30 +00:00
parent 8a4b71ba48
commit 044bf4f1e7
1 changed files with 16 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
pep-0003.txt
View File

@ -14,6 +14,13 @@ Introduction
a list of people willing to handle bug reports and their areas of a list of people willing to handle bug reports and their areas of
expertise. expertise.
These are guidlines for the developers of Python, not the
submitters of bugs. Those are at
http://docs.python.org/lib/reporting-bugs.html
(though this hardly seems the best place).
Guidelines Guidelines
@ -27,16 +34,18 @@ Guidelines
request", "later", and "closed"; and add a comment to the bug request", "later", and "closed"; and add a comment to the bug
saying that this is the case (mentioning the PEP explicitly). saying that this is the case (mentioning the PEP explicitly).
XXX do we prefer the feature request tracker or PEP 42?
3. Assign the bug a reasonable priority. We don't yet have a 3. Assign the bug a reasonable priority. We don't yet have a
clear sense of what each priority should mean, except than 9 is clear sense of what each priority should mean, except than 9 is
highest and 1 is lowest. One rule, however, is that bugs with highest and 1 is lowest. One rule, however, is that bugs with
priority seven or higher must be fixed before the next release. priority seven or higher must be fixed before the next release.
4. If a bug report doesn't have enough information to allow you to 4. If a bug report doesn't have enough information to allow you to
reproduce or diagnose it, send email to the original submittor reproduce or diagnose it, ask the original submitter for more
and ask for more information. If the original report is really information. If the original report is really thin and your
thin and your email doesn't get a response after a reasonable email doesn't get a response after a reasonable waiting period,
waiting period, you can close the bug. you can close the bug.
5. If you fix a bug, mark the status as "Fixed" and close it. In 5. If you fix a bug, mark the status as "Fixed" and close it. In
the comments, include the CVS revision numbers of the the comments, include the CVS revision numbers of the
@ -44,10 +53,9 @@ Guidelines
SourceForge bug number *and* a normal description of the SourceForge bug number *and* a normal description of the
change. change.
6. If you are assigned a bug that you are unable to deal with 6. If you are assigned a bug that you are unable to deal with,
assign it to someone else. The guys at PythonLabs get paid to assign it to someone else if you think they will be able to
fix these bugs, so pick one of them if there is no other deal with it, otherwise it's probably best to unassign it.
obvious candidate.
References References