Skip to main content

Python 1994: Recollections from the First Conference

We are happy to announce PyCon 2017’s Sunday morning plenary event — the final day of this year’s main conference will feature Guido van Rossum on a panel of Python programmers who attended the first-ever Python conference back in 1994! Paul Everitt will moderate the panel as they answer questions and share their memories about that first Python conference when the programming language was still young.

At the beginning of 1994, the World Wide Web consisted of less than 1,000 sites. There was no distributed version control. No public issue trackers. Programmers communicated their ideas, issues, and patches in plain text on mailing lists and Usenet newsgroups. The small community of Python programmers were connected through both a mailing list and the comp.lang.python newsgroup, which was busy enough that several new messages were appearing each day.

An exciting announcement blazed out to subscribers of the Python mailing list in September 1994: Guido van Rossum, the Dutch researcher who had invented Python, was going to visit the United States! An impromptu Python workshop was quickly organized for the beginning of November where Python programmers could for the first time meet each other in person.

Attendees of the first Python conference, in a tiny and highly artifacted JPEG that was typical of the era

Of the small group who gathered at NIST over November 1–3, 1994, several will be on stage to share about both the triumphs and the mistakes of those early years. The panel is currently slated to include:

  • Guido van Rossum
  • Paul Everitt (moderator)
  • Barry Warsaw
  • Jim Fulton

There is one way that you in the Python community can go ahead and start helping us prepare for the panel:

We need your questions!

You can go ahead and suggest questions by tweeting them with a hashtag of #nist1994. The panel will curate your tweeted questions along with questions that they solicit elsewhere, and will have their favorites ready for the panel at PyCon.

Thanks to Paul Everitt for organizing the panel, which will aim to spur not only nostaligia for a lost era but lessons, warnings, and inspirations for future generations of Python developers!

Comments

Popular posts from this blog

PyCon 2018 Registration is Now Open!

We’re thrilled to announce the opening of registration for PyCon 2018 in Cleveland, Ohio! The prior six PyCons have sold out, so prepare for another one and get your tickets early. The first 800 tickets sold are priced at an early bird discount, saving over 20% on corporate tickets and over 12% on individual tickets. Students save $25 if they purchase early!

To get started, create an account and head to https://us.pycon.org/2018/registration/ to get your tickets!

You get a package that is hard to beat when you register for PyCon. The conference itself is three days worth of our community’s 95 best talks, amazing keynote speakers each morning, and our famed lightning talks to close out each day, but it’s much more than that. It’s having over 3,000 people in one place to learn from and share with. It’s joining a conversation in the hallway with the creators of open source projects. It’s taking yourself from beginner to intermediate, or intermediate to advanced. For some, it’s getting st…

PyCon 2018 Code of Conduct Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. For 2018 the Code of Conduct underwent an extensive overhaul, our procedures for reporting and responding to incidents were improved, and our on-site methods were improved. You can read more about the updates for 2018 here. Cumulatively these changes were meant to improve the safety, welcoming nature, and overall inclusivity of PyCon. Based on initial responses, feedback, and incidents reported this year we feel that we made progress on those goals. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents. With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon…

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…