Day 3 went by rather quickly. The Keynote was given by Greg Stein, covering the topic of "Python at Google." Greg's been using Python for a LONG time and had some nice stories about using Python in corporate settings (including Microsoft.)
Google's use of Python is mostly in their build- and server-management tools, but they do have a few web toys (like http://code.google.com/ ) that are built with it. He said that Google uses Python because it's "highly adaptable," meaning that software requirements and computing environments can change without drastically hurting the development process.
In describing the time it takes for programmers to learn Python, he said something to the effect of, "[you can] read it in 2 hours, program in 2 days, [and] contribute to the company in 2 weeks." Fabulous.
For the web projects using Python, the meat of the work is still done in C , which is the most common programming language at Google. However, when the C code is built, the build system automatically uses SWIG to generate Python bindings for prototyping.
After the Google session, Jukka and I got ready for our presentation on Python for Series 60. After talking to people at the conference for a couple days, we decided that we should actually start the presentation by describing what Series 60 actually is. In hind-sight, we probably should have titled the presentation "Python on your phone." I was a little disappointed that we didn't have enough time to cover everything we wanted, but fortunately we had a lot of really good conversations in the hallways after the presentation.
After lunch I headed back to the Lightning Talks, and once again, there were some great projects presented. My personal favorite this time was the demo of rlcompleter2. Amazing!
To wrap up the day I went to Ted Leung's presentation on PyBlosxom. I've been thinking more lately about moving my blog over to PyBlosxom, and thankfully, the session answered a few questions I'd had.
After the session I had to run to the airport, but amazingly enough, I'm actually on a plane (right now) and we're on schedule. A delay out of D.C. made me almost miss my connection, but I made it right as they were closing the gate. So I'm 1-in-4 now for getting home on time this month... we'll see how next week goes.