Let’s meet up in Atlanta at PyWorks!


This year has seemed like a big year for Python conference activity in the US. Of course, there was PyCon in March, which topped 1,000 attendees. I’ve also seen announcements for a bunch of regional Python gatherings (like PyOhio, which was close by but I couldn’t attend).

This year, we also get PyWorks, which is joined at the hip with php|works in Atlanta in November. This is the first year for PyWorks, and they’ve got a good lineup going. There’s a day of tutorials and two days of talks, so this is more like a PyCon than it is like those regional conferences.

In addition to attending talks myself, I’m hoping to meet some more good Python and/or JavaScript folks in the “hallway track”. I’m sure there will be lots of Dojo users mixed in with the Python and PHP people, so we should get together.

I have four speaking slots (one of which isn’t listed yet) over the two conference days (gadzooks!). I’ll be doing a revised and expanded version of my PyCon talk “Rich Client Web Applications with TurboGears 2 and Dojo”. I’ll also be giving an updated version of the “Easy build and deployment automation with Paver” talk that Mark Ramm gave in my stead at PyOhio. Paver really puts the “scripting” back in “Python scripting language” (Python certainly does a lot more than “scripting”!)

I’ll also be giving a talk called “ZODB: The Most Underappreciated Library in Python”. The ZODB is great. More people should use it. This is a talk I gave a couple months back at MichiPUG, so it’s only been seen by a small group at this point.

My fourth talk is one I haven’t given anywhere before: “Beyond the Source: Growing Your Community”. I’m going to talk in concrete terms about things you can do to grow an open source community. Open source projects really need to get to a certain level of use before they become viable open source projects, and there are many, many ways in which people interested in a project can help it get there.

I hope to see you there!

4 thoughts on “Let’s meet up in Atlanta at PyWorks!”

  1. I’m looking forward to your ZODB talk. It seems like a great library, but is it really true that some features require buying the “enterprise” version?

    I’ve been playing around with CouchDB too. I’m not too deep into either ZODB or CouchDB, but at this point, I think I could use CouchDB for most everything I could use ZODB for, with the extra bonus that CouchDB has some pretty fancy scalability powers.

    Still a rookie in both technologies.

  2. For everything I’ve needed it for, the ZODB has been free. I haven’t gone into high-scalability situations with it, however. Scalability is one of those things where one size definitely does not fit all… Depends on the application.

    Given today’s hardware, many, many applications don’t have scalability concerns any more. Not everyone is building Twitter. That’s one of my points about the ZODB. It makes life so much easier for apps where scaling doesn’t matter. When scaling does matter, the ZODB may still be just fine, but it depends on the app.

  3. I wouldn’t worry to much about that. Consider that ZEO is open source and gives you a bunch of scalability:


    There’s an open source “relstorage” now for putting an RDBMS at the backend, so that you can use the scaling features of the relational database, if that meets your needs.

    The commercial bit is Zope Replication Services (ZRS) which is around if you really need it. If you need to scale to the point where the free stuff is not doing the job for you, then you’d better have some money around because you’ve probably got a whole bunch of things to worry about.

Comments are closed.