traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update the instructions on reporting bugs to reflect that anonymous reports 

are no longer accepted.
This commit is contained in:
Fred Drake 2002-02-04 21:43:08 +00:00
parent baf43c5036
commit c121745fda
1 changed files with 6 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Doc/texinputs/reportingbugs.tex
View File

@ -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 developers would like to know of any deficiencies you find in Python
or its documentation. 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 All bug reports should be submitted via the Python Bug Tracker on
SourceForge (\url{http://sourceforge.net/bugs/?group_id=5470}). The SourceForge (\url{http://sourceforge.net/bugs/?group_id=5470}). The
bug tracker offers a Web form which allows pertinent information to be bug tracker offers a Web form which allows pertinent information to be
entered and submitted to the developers. 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 The first step in filing a report is to determine whether the problem
has already been reported. The advantage in doing so, aside from has already been reported. The advantage in doing so, aside from
saving the developers time, is that you learn what has been done to 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''). (such as ``Documentation'' or ``Library'').
Each bug report will be assigned to a developer who will determine 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 what needs to be done to correct the problem. You will
SourceForge account and logged in to report the problem, you will
receive an update each time action is taken on the bug. receive an update each time action is taken on the bug.