mirror of
https://github.com/python/cpython.git
synced 2026-01-29 02:32:18 +00:00
Bug #1010: docs url points to SF.net, now points to bugs.python.org.
This commit is contained in:
parent
8e3315d5ae
commit
906f735bb0
1 changed files with 9 additions and 10 deletions
|
|
@ -10,8 +10,8 @@ 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
|
||||
All bug reports should be submitted via the Python Bug Tracker at
|
||||
(\url{http://bugs.python.org}). The
|
||||
bug tracker offers a Web form which allows pertinent information to be
|
||||
entered and submitted to the developers.
|
||||
|
||||
|
|
@ -21,25 +21,24 @@ saving the developers time, is that you learn what has been done to
|
|||
fix it; it may be that the problem has already been fixed for the next
|
||||
release, or additional information is needed (in which case you are
|
||||
welcome to provide it if you can!). To do this, search the bug
|
||||
database using the search box on the left side of the page.
|
||||
database using the search box on the top side of the page.
|
||||
|
||||
If the problem you're reporting is not already in the bug tracker, go
|
||||
back to the Python Bug Tracker
|
||||
(\url{http://sourceforge.net/bugs/?group_id=5470}). Select the
|
||||
``Submit a Bug'' link at the top of the page to open the bug reporting
|
||||
back to the Python Bug Tracker. Select the
|
||||
``Create new'' link at the left of the page to open the bug reporting
|
||||
form.
|
||||
|
||||
The submission form has a number of fields. The only fields that are
|
||||
required are the ``Summary'' and ``Details'' fields. For the summary,
|
||||
required are the ``Title'' and ``Type'' fields. For the title,
|
||||
enter a \emph{very} short description of the problem; less than ten
|
||||
words is good. In the Details field, describe the problem in detail,
|
||||
words is good. In the ``Change Note'' field, describe the problem in detail,
|
||||
including what you expected to happen and what did happen. Be sure to
|
||||
include the version of Python you used, whether any extension modules
|
||||
were involved, and what hardware and software platform you were using
|
||||
(including version information as appropriate).
|
||||
|
||||
The only other field that you may want to set is the ``Category''
|
||||
field, which allows you to place the bug report into a broad category
|
||||
The only other field that you may want to set is the ``Components''
|
||||
field, which allows you to place the bug report into broad categories
|
||||
(such as ``Documentation'' or ``Library'').
|
||||
|
||||
Each bug report will be assigned to a developer who will determine
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue