Following up two tutorial and summit days, then three days of the conference, the sprints got off to a great start on Sunday evening. I'm back at home now but wanted to put together a summary of the first two days: A lot of great projects got up on stage to pitch their sprint ideas including Brett Cannon speaking for CPython, letting people know where the sprint would be, mentioning the "dev-in-a-box" CDs, and encouraging people to come out and hack. Within 15 minutes of the end of announcements, we had 7 first-time sprinters eager to dive in and get going right away. The new developer guide was instrumental in getting everyone through the initial setup. The plan was to get a Mercurial checkout and coverage.py as a starting point, as one of the suggested sprint targets was increasing test coverage. By 6:30 on the first day, we were up to 9 people fully up and running, pouring over the coverage results (which were handily pre-generated on the "dev-in-a-box" CD), and diving into code. Here's what everyone worked on:
stringtests and got a patch written and checked in within first day.
urllibtests on his Mac and got to work on fixing them. After that he started on increasing
dbmpatch he made a few days before the sprint, then got it reviewed and checked in. He followed that up with test coverage patches to
test_email_codecsto Python 3. He's also working on
cgitbup to 75% test coverage by starting a test suite for it.
tarfilefor test coverage and a few bugs.
unittestissue and wrote up a fix plus tests that got checked in pretty quickly. He's also working on
pydocissue that was being discussed on the mailing list about named tuples
coverageand ended up diving into the order of imports on interpreter startup to fix coverage results before going further with them. He took the new results and is working on