\label{reporting-bugs} Python is a mature programming language which has established areputation for stability.  In order to maintain this reputation, thedevelopers would like to know of any deficiencies you find in Pythonor its documentation. Before submitting a report, you will be required to log into SourceForge;this will make it possible for the developers to contact youfor additional information if needed.  It is not possible to submit abug report anonymously. All bug reports should be submitted via the Python Bug Tracker onSourceForge (\url{http://sourceforge.net/bugs/?group_id=5470}).  Thebug tracker offers a Web form which allows pertinent information to beentered and submitted to the developers. The first step in filing a report is to determine whether the problemhas already been reported.  The advantage in doing so, aside fromsaving the developers time, is that you learn what has been done tofix it; it may be that the problem has already been fixed for the nextrelease, or additional information is needed (in which case you arewelcome to provide it if you can!).  To do this, search the bugdatabase using the search box on the left side of the page. If the problem you're reporting is not already in the bug tracker, goback 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 reportingform. The submission form has a number of fields.  The only fields that arerequired are the ``Summary'' and ``Details'' fields.  For the summary,enter a \emph{very} short description of the problem; less than tenwords is good.  In the Details field, describe the problem in detail,including what you expected to happen and what did happen.  Be sure toinclude the version of Python you used, whether any extension moduleswere 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(such as ``Documentation'' or ``Library''). Each bug report will be assigned to a developer who will determinewhat needs to be done to correct the problem.  You willreceive an update each time action is taken on the bug.  \begin{seealso}  \seetitle[http://www-mice.cs.ucl.ac.uk/multimedia/software/documentation/ReportingBugs.html]{How        to Report Bugs Effectively}{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.}   \seetitle[http://www.mozilla.org/quality/bug-writing-guidelines.html]{Bug        Writing Guidelines}{Information about writing a good bug        report.  Some of this is specific to the Mozilla project, but        describes general good practices.}\end{seealso}