diff options
| author | Fred Drake <fdrake@acm.org> | 2002-02-04 21:43:08 (GMT) |
|---|---|---|
| committer | Fred Drake <fdrake@acm.org> | 2002-02-04 21:43:08 (GMT) |
| commit | c121745fda6809bebc9a831dd27325f486086781 (patch) | |
| tree | 5f9f46eb7827fd5ba8b2199608762fc1648748d9 /Doc/texinputs | |
| parent | baf43c5036f2811b46dd1cdd2a0341f022f8ec49 (diff) | |
| download | cpython-c121745fda6809bebc9a831dd27325f486086781.zip cpython-c121745fda6809bebc9a831dd27325f486086781.tar.gz cpython-c121745fda6809bebc9a831dd27325f486086781.tar.bz2 | |
Update the instructions on reporting bugs to reflect that anonymous reports
are no longer accepted.
Diffstat (limited to 'Doc/texinputs')
| -rw-r--r-- | Doc/texinputs/reportingbugs.tex | 16 |
1 files changed, 6 insertions, 10 deletions
diff --git a/Doc/texinputs/reportingbugs.tex b/Doc/texinputs/reportingbugs.tex index c06470a..6db43de 100644 --- a/Doc/texinputs/reportingbugs.tex +++ b/Doc/texinputs/reportingbugs.tex @@ -5,19 +5,16 @@ reputation for stability. In order to maintain this reputation, the developers would like to know of any deficiencies you find in Python or its documentation. +Before submitting a report, you will be required to log into SourceForge; +this will make it possible for the developers to contact you +for additional information if needed. It is not possible to submit a +bug report anonymously. + All bug reports should be submitted via the Python Bug Tracker on SourceForge (\url{http://sourceforge.net/bugs/?group_id=5470}). The bug tracker offers a Web form which allows pertinent information to be entered and submitted to the developers. -Before submitting a report, please log into SourceForge if you are a -member; this will make it possible for the developers to contact you -for additional information if needed. If you are not a SourceForge -member but would not mind the developers contacting you, you may -include your email address in your bug description. In this case, -please realize that the information is publically available and cannot -be protected. - The first step in filing a report is to determine whether the problem has already been reported. The advantage in doing so, aside from saving the developers time, is that you learn what has been done to @@ -46,8 +43,7 @@ field, which allows you to place the bug report into a broad category (such as ``Documentation'' or ``Library''). Each bug report will be assigned to a developer who will determine -what needs to be done to correct the problem. If you have a -SourceForge account and logged in to report the problem, you will +what needs to be done to correct the problem. You will receive an update each time action is taken on the bug. |