Skip to main content

Sprint status reports

The sprinters gave brief reports on their work at a session just before lunch today. This session was a last minute addition to the schedule, and I arrived most of the way through Ted Leung's talk on the Chandler sprint. I mentioned the distutils sprint in a previous post.

What is a sprint?
A sprint is a focused development session, in which developers pair in a room and focus on building a particular subsystem. A sprint is organized with a coach leading the session. The coach sets the agenda, tracks activities, and keeps the development moving. The developers work in pairs using XP's pair programming approach.
Barry Warsaw talked about the Mailman 3 sprint. He recommends SQLObject as an object-relational mapping that allows you to write your classes in idiomatic Python. SQLObject generates SQL code automatically.

There were several Zope-related sprints. Jim Fulton reported on some ZODB and Zope work. Tim Peters and Christian Theune added blob support to ZODB and ZEO. Zope had problems handling large files (like multi-MB source code distributions) -- performance and memory consumption were big problems. The blob support basically puts large object on the local filesystem and integrates regular file modifications with the transaction machinery. Christian also did some basic code maintenance on ZODB.

Garrett Smith and Babu (? didn't catch his last name) made some great improvements to the pluggable authentication mechanism in Zope3.

Michael Bernstein and Andy Dustman spent several days writing a weblog application for Zope3. There are basic blog posts and Atom feeds. It took a long time because they used the Dublic Core metadata in the add and update mechanism for post. It was hard to get the schema working correctly. It was hard to get into adapters and interfaces. The resulting code ended up being small, but they had to delete a lot of code. "Zope 3 is a lot easier to read than it is to write."

Mike McLay reported on a sprint involving students from three different Arlington county high schools. (Two different schools use Python as a teaching language.) They worked on a school tool
application; they did more design than writing code. They are updating an old-style Zope application to use page templates and an external backend database. They learned about SQLObject at the sprint, from the Mailman group, and started using it.

Brett Cannon, author of the python-dev summaries for the last two years, worked on the AST branch for a few days. The big goal of the sprint was to document the design for the Python compiler. I started the AST branch a couple of years ago, but never wrote a proper design
doc. John Ehrseman is working on decorators, and Nick Coghlan is working (from his home) on generator expressions. It sounds like the work to upgrade the branch to Python 2.4 is nearly complete. What's left is the rather tedious work of testing and verifying that error handling is correct. It looks like the basic design document is in good shape, though.

I didn't catch the details of the PyPy sprint, except that they got the pickle tests running and uncovered some problems with the implementation of new-style classes. New-style classes are largely undocumented, so this isn't much of a surprise. The pickle support is deeply integrated with new-style classes, because pickle needs to create and initialize objects (including immutable objects) and introspects on them to discover the object state. Several people of the PyPy project have observed that their implementation of new-style classes is sufficiently high level that it could be the good starting point for a specification; it's easier to read the intent of the Python code than it is of the C code.

Comments

Popular posts from this blog

PyCon 2018 Registration is Now Open!

We’re thrilled to announce the opening of registration for PyCon 2018 in Cleveland, Ohio! The prior six PyCons have sold out, so prepare for another one and get your tickets early. The first 800 tickets sold are priced at an early bird discount, saving over 20% on corporate tickets and over 12% on individual tickets. Students save $25 if they purchase early!

To get started, create an account and head to https://us.pycon.org/2018/registration/ to get your tickets!

You get a package that is hard to beat when you register for PyCon. The conference itself is three days worth of our community’s 95 best talks, amazing keynote speakers each morning, and our famed lightning talks to close out each day, but it’s much more than that. It’s having over 3,000 people in one place to learn from and share with. It’s joining a conversation in the hallway with the creators of open source projects. It’s taking yourself from beginner to intermediate, or intermediate to advanced. For some, it’s getting st…

Python Education Summit celebrates its 6th year in 2018

Teachers, educators, and Python users: come and share your projects, experiences, and tools of the trade you use to teach coding and Python to your students. The Annual Python Education Summit is held in conjunction with PyCon 2018, taking place on Thursday May 10. Our Call for Proposals is open until January 3rd, and we want to hear from you! See https://us.pycon.org/2018/speaking/education-summit/ for more details.

What we look for in Education Summit talks are ideas, experiences, and best practices on how teachers and programmers have implemented instruction in their schools, communities, books, tutorials, and other places of learning by using Python.

Have you implemented a program that you've been dying to talk about?Have you tried something that failed but learned some great lessons that you can share?Have you been successful implementing a particular program?
We urge anyone in this space to submit a talk! We’re looking for people who want to share their knowledge and leverage…

How to get ready for the PyCon development sprints

[A guest post by Kushal Das, one of the 2016 Sprint Coordinators]So — you have already decided to join in the PyCon development sprints! The sprints run for four days, from Thursday to Sunday after the conference. You do not have to be registered for the conference to attend the sprints! Some teams plan to write code over all four days, while some projects plan a shorter sprint if the organizers cannot stay for all four days.Can you start getting prepared for the sprint ahead of time? Yes!There are several things you can do ahead of time, that can save effort once you arrive at the sprints — and some preparations can even be made at home, before you arrive at PyCon:Have your operating system updated and patched — whether Mac, Windows, or Linux. This eliminates one possible source of problems with getting software up and running.Go ahead and install the version control system that will be used by the projects you are interested in. If you install both git and Mercurial on your computer…