Home ›

PyCon DC 2003

Apr 15, 2003  By Mike Orr
 in
A wrapup of what happened at this year's Python conference, a DIY conference organized by Python enthusiasts to catch up on new projects and discuss the future.
Conclusion

The first PyCon was a success. People liked the relatively loose schedule that allowed time for private and spontaneous meetings. They were enthusiastic about the new ideas: open space and the sprints. The only complaints I heard were of a "we'll do better next time" variety: the food was the same every day; there was too much food (Guido's picture) considering some registrants had to leave early and others don't show up at all; the registration system for on-site registrants didn't work right; the last day was a little slow; the 15-minute refereed paper-sessions were too short. But none of these were show stoppers, and it was an impressive achievement for Python's first amateur-run conference. More than one person commented that this will likely become Python's "working" conference, the one where development gets done or planned, while others, such as OSCon, will serve mainly to promote Python to those going to those conferences anyway.

A final note to Pythoneers: the theme of PyConDC 2003 was Popularizing Python, and that's also a goal of the Python Software Foundation this year. Now you have learned. Go forth and do something with it.

Resources

PyCon Web Page

Wiki

Another View of the Wiki

Links to the Refereed Papers

It Fits Your Brain: the Ninth Annual International Python Conference

Import This: the Tenth International Python Conference

Pictures from the Conference

Mike Orr writes Python articles for Linux Journal and is the Editor of our sister publication Linux Gazette.

email: mso@oz.net

______________________

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Links to the Refereed Papers - Updated

Anonymous's picture
Submitted by Anonymous (not verified) on Wed, 07/01/2009 - 03:33.

Try :

PyCon 2003 Papers

Re: PyCon DC 2003

Anonymous's picture
Submitted by Anonymous on Wed, 04/16/2003 - 02:00.

Nice article, but two mistakes:

  • Zope3 does as yet does not use Twisted in any way. There are
    plans to this effect but nobody has yet stepped up to do the
    work.
  • PyCon while very nice was not Python's first amateur run
    conference. There were various smaller ones in the past,
    but EuroPython 2002 was entirely volunteer run and had
    in fact more attendees than PyCon. You can imagine that
    hearing this claim (now the second time) is rather frustrating
    to those volunteers (me included). I guess it
    could be taken as a compliment that so many people
    apparently think EuroPython was professionally organized. :)

Martijn Faassen

Webcast
More Resources
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.

Learn More

Sponsored by AMD

White Paper
More Resources
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions