2007-08-15 11:28:01 -03:00
|
|
|
.. _reporting-bugs:
|
|
|
|
|
|
|
|
|
|
************************
|
|
|
|
|
Reporting Bugs in Python
|
|
|
|
|
************************
|
|
|
|
|
|
|
|
|
|
Python is a mature programming language which has established a reputation for
|
|
|
|
|
stability. In order to maintain this reputation, the developers would like to
|
|
|
|
|
know of any deficiencies you find in Python.
|
|
|
|
|
|
2008-08-24 18:55:03 -03:00
|
|
|
Bug reports should be submitted via the Python Bug Tracker
|
2007-08-15 11:28:01 -03:00
|
|
|
(http://bugs.python.org/). The bug tracker offers a Web form which allows
|
|
|
|
|
pertinent information to be entered and submitted to the developers.
|
|
|
|
|
|
|
|
|
|
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 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 top of the page.
|
|
|
|
|
|
Merged revisions 72319-72320,72467,72661,72675-72679,72703,72708,72710,72712,72801-72802,72820,72822,72824,72826-72828,72830 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/trunk
........
r72319 | georg.brandl | 2009-05-05 10:28:49 +0200 (Di, 05 Mai 2009) | 1 line
#1309567: fix linecache behavior of stripping subdirectories from paths when looking for relative filename matches. Also add a linecache test suite.
........
r72320 | georg.brandl | 2009-05-05 10:30:28 +0200 (Di, 05 Mai 2009) | 1 line
Add a news entry for r72319.
........
r72467 | georg.brandl | 2009-05-08 14:17:34 +0200 (Fr, 08 Mai 2009) | 1 line
Fix name.
........
r72661 | georg.brandl | 2009-05-15 10:03:03 +0200 (Fr, 15 Mai 2009) | 1 line
Fix example output for doctest-like demos.
........
r72675 | georg.brandl | 2009-05-16 13:13:21 +0200 (Sa, 16 Mai 2009) | 1 line
#6034: clarify __reversed__ doc.
........
r72676 | georg.brandl | 2009-05-16 13:14:46 +0200 (Sa, 16 Mai 2009) | 1 line
#6025: fix signature of parse().
........
r72677 | georg.brandl | 2009-05-16 13:18:55 +0200 (Sa, 16 Mai 2009) | 1 line
#6009: undocument default argument of Option as deprecated.
........
r72678 | georg.brandl | 2009-05-16 13:21:29 +0200 (Sa, 16 Mai 2009) | 1 line
#2856: document 2.x os.listdir() behavior for undecodable filenames.
........
r72679 | georg.brandl | 2009-05-16 13:24:41 +0200 (Sa, 16 Mai 2009) | 1 line
Fix about and bugs pages to match real workflow.
........
r72703 | georg.brandl | 2009-05-17 10:10:27 +0200 (So, 17 Mai 2009) | 1 line
part of #4144: fix exception message in console session.
........
r72708 | georg.brandl | 2009-05-17 10:24:29 +0200 (So, 17 Mai 2009) | 1 line
#6017: better document behavior of dictiterators when the dict is changed.
........
r72710 | georg.brandl | 2009-05-17 10:36:04 +0200 (So, 17 Mai 2009) | 1 line
#5942: Copy over flag table from dbm.rst which is clearer.
........
r72712 | georg.brandl | 2009-05-17 10:55:00 +0200 (So, 17 Mai 2009) | 1 line
#5935: mention that BROWSER is looked for in PATH.
........
r72801 | georg.brandl | 2009-05-20 20:31:14 +0200 (Mi, 20 Mai 2009) | 1 line
#6055: refer to "sqlite3" consistently.
........
r72802 | georg.brandl | 2009-05-20 20:35:27 +0200 (Mi, 20 Mai 2009) | 1 line
#6051: refer to email examples for better way to construct email messages.
........
r72820 | georg.brandl | 2009-05-22 09:23:32 +0200 (Fr, 22 Mai 2009) | 1 line
Use raise X(y).
........
r72822 | georg.brandl | 2009-05-22 11:33:25 +0200 (Fr, 22 Mai 2009) | 1 line
#6084: fix example.
........
r72824 | georg.brandl | 2009-05-22 11:43:17 +0200 (Fr, 22 Mai 2009) | 1 line
Fix references to file-related functions and methods (os.* vs file.*).
........
r72826 | georg.brandl | 2009-05-22 11:49:42 +0200 (Fr, 22 Mai 2009) | 1 line
Fix confusing wording.
........
r72827 | georg.brandl | 2009-05-22 11:50:30 +0200 (Fr, 22 Mai 2009) | 1 line
s/use/call/
........
r72828 | georg.brandl | 2009-05-22 11:58:48 +0200 (Fr, 22 Mai 2009) | 1 line
Correction in softspace behavior description.
........
r72830 | georg.brandl | 2009-05-22 12:40:00 +0200 (Fr, 22 Mai 2009) | 1 line
#6086: fix spelling and use a better exception to catch.
........
2009-05-26 06:04:23 -03:00
|
|
|
In the case of documentation bugs, look at the most recent development docs at
|
|
|
|
|
http://docs.python.org/dev to see if the bug has been fixed.
|
|
|
|
|
|
2007-08-15 11:28:01 -03:00
|
|
|
If the problem you're reporting is not already in the bug tracker, go back to
|
|
|
|
|
the Python Bug Tracker. If you don't already have a tracker account, select the
|
|
|
|
|
"Register" link in the sidebar and undergo the registration procedure.
|
|
|
|
|
Otherwise, if you're not logged in, enter your credentials and select "Login".
|
|
|
|
|
It is not possible to submit a bug report anonymously.
|
|
|
|
|
|
|
|
|
|
Being now logged in, you can submit a bug. Select the "Create New" link in the
|
|
|
|
|
sidebar to open the bug reporting form.
|
|
|
|
|
|
|
|
|
|
The submission form has a number of fields. For the "Title" field, enter a
|
|
|
|
|
*very* short description of the problem; less than ten words is good. In the
|
|
|
|
|
"Type" field, select the type of your problem; also select the "Component" and
|
|
|
|
|
"Versions" to which the bug relates.
|
|
|
|
|
|
2008-05-04 16:10:02 -03:00
|
|
|
In the "Comment" field, describe the problem in detail, including what you
|
2007-08-15 11:28:01 -03:00
|
|
|
expected to happen and what did happen. Be sure to include whether any
|
|
|
|
|
extension modules were involved, and what hardware and software platform you
|
|
|
|
|
were using (including version information as appropriate).
|
|
|
|
|
|
|
|
|
|
Each bug report will be assigned to a developer who will determine what needs to
|
|
|
|
|
be done to correct the problem. You will receive an update each time action is
|
|
|
|
|
taken on the bug.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
.. seealso::
|
|
|
|
|
|
2008-01-21 14:41:24 -04:00
|
|
|
`How to Report Bugs Effectively <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>`_
|
2007-08-15 11:28:01 -03:00
|
|
|
Article which goes into some detail about how to create a useful bug report.
|
|
|
|
|
This describes what kind of information is useful and why it is useful.
|
|
|
|
|
|
2008-03-14 21:20:19 -03:00
|
|
|
`Bug Writing Guidelines <http://developer.mozilla.org/en/docs/Bug_writing_guidelines>`_
|
2007-08-15 11:28:01 -03:00
|
|
|
Information about writing a good bug report. Some of this is specific to the
|
|
|
|
|
Mozilla project, but describes general good practices.
|
|
|
|
|
|
