NOTE: For updated instructions please refer to the devguide.

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.

Bug reports should be submitted via the Python Bug Tracker The bug tracker offers a Web form which allows pertinent information to be entered and submitted to the developers.

Filing a Report

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 tracker box on the top of the page.

Log In

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. If you have an account already, enter your credentials and select Login. It is not possible to submit a bug report anonymously.

Once you're logged in, you can submit a bug.

Create an Issue

Select the Create New link in the sidebar to open the bug reporting form.

The submission form has a number of fields.

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).

Click submit

Some pointers to keep in mind:

Understanding the usual Issue Workflow also helps in creating good bug reports, raising the chances of your bug report (or feature request) being resolved efficiently.

What happens next

See Issue Workflow and general Roundup guidelines for detailed descriptions of how bugs get fixed.

Each bug report will ultimately be assigned to a core developer who will determine what needs to be done to correct the problem or take the necessary steps to include a provided fix or patch into the Python source. You will receive an email update each time action is taken on the bug (it's possible to opt-out). Further editing and new messages can be done by the web form. You can also post to issues by replying to an email that you receive, file uploads can be done via attachments in this case.

Contributions in the form of tests, docs and patches are very welcome. The Developer Documentation is your main guide to the procedures and tools of the trade. The PythonBugDay volunteer docs offers an overview focused at newcomer developers.

see also:

How to Report Bugs Effectively

Bug Writing Guidelines

SubmittingBugs (last edited 2012-06-17 11:23:14 by host213-157-dynamic)

Unable to edit the page? See the FrontPage for instructions.