In addition to Guido van Rossum, whose entertaining keynote addressed the answers he gives to frequently asked questions, half a dozen Google engineers had the opportunity to present in the conference technical tracks. Augie Fackler and Nathaniel Manista, for example, delivered an introductory talk titled “Stop Mocking Start Testing” that discussed lessons learned about testing python code over the many years since Google Code originally launched. Of course, Google Code itself hosts many projects, among which is “gaeunit,” a project for testing python code.
The Friday evening party sponsored by YouTube, New Relic, Loggly, Rackspace, and Skullcandy at the Hyatt Regency Santa Clara had opportunities for lots of thought provoking discussions.
Google was a platinum sponsor, but what seemed to draw the most interest was this year’s edition of the Google at PyCon challenge. Just like past years, the challenges were relevant to the conference’s Python topic. Even before the exhibit floor opened, many attendees had obviously been hard at work on the problems and were already prepared to head straight to the booth and show off their solutions. The next morning, the same rush arrived from people who had worked on the problems overnight.
Between bursts of excited game participants, the booth was a casual place to hang out and chat about interesting Python challenges with whoever else happened to be around. A comfy red couch was certainly a draw, often for those whose competition submission had a bug in it.
A few of the Google attendees who happened to be in the booth at the same time |
After three days, the conference drew to a close. One lucky attendee won a dancing robot, and then the PyCon event moved into its next phase, the sprints. While many left, hundreds of people remained to form focused groups to develop key improvements in Python technologies.
Posted by Alex Perry, Site Reliability Engineer
Add a comment