PythonBugDay - Python Wiki (original) (raw)

(!) Next Python Bug Day: November 3rd

Time: all Saturday

Join us for an effort at closing some Python bugs and patches. Get quick feedback on your patches and bugfixes, or learn how to submit and examine patches.

To get all set up, the Developer's Guide contains all the information you need.

There are usually a few core developers around at any time. Here are the nicknames of developers who will be present for sure:

• merwok — Éric Araujo — American East Coast timezone

Participating at Your User Group

The Montréal-Python user group will meet up in person to participate in the bug day. Some Python user groups will meet up in person during the weekend.

Is your local user group participating?

Participating Online

Participants will meet in the #python-dev IRC channel on irc.freenode.net. To learn more about IRC and to find links to IRC clients for various platforms, see http://www.irchelp.org.

Finding Bugs

Using the bug tracker, you can perform various searches to look for candidate issues:

• Bugs classified as 'easy'
• Documentation bugs
• Random issue (you can use the link in the left sidebar of the bug tracker to go through random issues until you find one that you like

Procedures

The goal of the bug day is to process bug reports in the Python bug tracker, trying to fix and close issues.

What to do:

• Grab a copy of the Python codebase from Mercurial, following instructions in the Developer's Guide, and compile it.
• If you have a problem that isn't in the bug tracker, announce it to the IRC channel, and if it's more than five minutes' work, create a bug report for it. See the bug reporting instructions to learn how to write bug reports.
• When you choose a bug to work on, announce it to the IRC channel (e.g. "I'm working on #123456.") or on the bug report itself. This avoids accidentally duplicating work.
• Consider providing a patch that fixes the problem, or at least a simple test case that demonstrates the bug. Please see the patch submission guidelines in the Developer's Guide before submitting a patch.
• Does the bug appear to be gone in the Python development version (the Mercurial branch "default", that will become 3.4), but not the 3.2, 3.3 or 2.7 maintenance branchs? Report that, too.
• If someone else has supplied a fix, see if this fix works for² you, and add your results to the bug.
• Read the text of proposed patches and assess them for correctness and code quality. This is usually the most time-consuming step in the bug fixing process, so reading patches is very useful.
• If there's a working fix, feel free to add a note asking for the fix to get committed. The bug tracker has a lot of items in it, and it's easy for bugs to be overlooked.
• Feature requests should be classified as type 'feature request' in the bug tracker.

Questions?

If you have questions about the bug day, please add them to this section.

Previous bug days

Preparatory Tasks

• Need to set up log of python-dev channel
• Send announcements (python-announce, python-dev, PSF weblog, personal web log. python-list?)