Skip to main content

PyCon 2007 is over

PyCon 2007 is now over. At-the-door registration was surprisingly stronger than we had been expecting, and the final attendance figure was 593 registered attendees, a 44% increase from 2006.

The conference ran smoothly -- there were no disasters, only the odd oversight on our part or minor glitches. I personally heard from many attendees who really liked the balance of this year's conference: the daily lightning talk sessions, the selection of keynote speakers, and the featured talks. The rooms mostly didn't seem overly crowded to me, though we'll have to see what the feedback form results say. Jeff Rush and I are both very pleased with the conference, and are glad that the attendees seem to agree.

And now for the sprints...


Douglas said…
That is 593 attendees.
Catherine said…
Glory to you ( + Jeff, etc. ) for ever and ever, Andrew; it was absolutely fantastic. My coworkers can see that I'm floating this morning, still in a cloud of Pythony bliss.
Christian said…
Great job all around. It was my first PyCon and it won't be my last.
Mike said…
Kudos to all involved. Next year's PyCon can't come soon enough!
ogghead said…
I had an outstanding time, better than last year. Thanks, Andrew, for all the hard work you did.

(Catherine, email me about the Oracle-SQLAlchemy article I said I'd write. I'll get it done.)

One complaint: I've now tried three of the four recommended methods to get my "Release Form" accepted so my "XRC and wxPython" materials can be released. In fact, I did this well before the conference. No joy. I give up.
A.M. Kuchling said…
ogghead: sorry for the difficulty. It should have been as simple as asking for a recording form, signing it, and leaving it as the registration desk.
Do you have a signed registration form, or did you never get one?
Douglas said…
Note on uploading the release forms:

After the release form is uploaded, Jeff Rush or another system administrator needs to first sign off on the uploaded file. If you are having problem uploading the file send e-mail to with full information on the nature of the problem.
ogghead said…
Thanks, amk and doug. I had faxed a form a week before the conference, and Mike Muller handed in the second one I signed on Sunday. I emailed one to Jeff R and sent a followup email, but never heard back.

No worries--I'll try to upload a scanned image version and I'll email the pycon address and get it taken care of.

I wish I'd had the foresight and personal leeway to attend the sprints. Next year I will. PyCon was a major success, and thanks again!
Carl said…
2 words: THANK YOU!

Popular posts from this blog

PyCon 2018 Call for Proposals is Open!

It’s here! PyCon 2018’s Call for Proposals has officially opened for talks, tutorials, posters, and education summit presentations. PyCon is made by you, so we need you to share what you’re working on, how you’re working on it, what you’ve learned, what you’re learning, and so much more.

Before we dive in, the deadlines:
Tutorial proposals are due November 24, 2017.Talk, Poster, and Education Summit proposals are due January 3, 2018.Who should write a proposal? Everyone!

If you’re reading this post, you should write a proposal. PyCon is about uniting and building the Python community, and we won’t advance as an open community if we’re not open with each other about what we’ve learned throughout our time in it. It isn’t about being the smartest one in the room, so we don’t just pick all of the expert talks. It’s about helping everyone move together. “A rising tide lifts all boats,” if you will.

We need beginner, intermediate, and advanced proposals on all sorts of topics. We also need b…

PyCon 2018 Launches New Site, Sponsorship Search

After two great years in Portland, PyCon is shipping off to Cleveland for the 2018 and 2019 renditions of the Python community's largest gathering. PyCon 2018 will take place May 9 through 17 with two days of tutorials, three days of talks, and four days of development sprints.

For more information, check out our newly refreshed website at and follow us here on the blog and at @pycon on Twitter.

New Website

The new site features a design centered on the historic landmark Terminal Tower, a 52 story skyscraper that overlooks downtown Cleveland. When it opened in 1930, the tower was the fourth tallest building in the world and the tallest building outside of New York City. Though its height no longer tops the charts, the tower and surrounding Tower City area remain highly important to the city. What once was a beacon to guide ship captains to Cleveland's port and airplane pilots to its airport, the tower now includes 508 LEDs that light up for the holida…

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…