Skip to main content

PyCon 2011: Interview with Dave Beazley

It’s not the first time Dave Beazley made the drive from Chicago to PyCon, but it’s the first time he buckled up a piece of history to join him on the trip. After giving two tutorials on Python 3, Dave brings out his 1979 OSI Superboard II for an old school meets new school mashup which is sure to raise a few eyebrows and bring back memories for some.

“The Superboard II was the first computer on which I learned to program back in the late 70s,” said Dave when asked how he came about the machine. It sat in his parents’ basement until Eric Floehr mentioned it at a recent SciPy conference. From there he called his brother who brought it out to Chicago, and “much to our amazement, it still worked.”

After figuring out the cassette audio interface, his concurrency and distributed computing interests had to find a way in. He decided to use ZeroMQ and Redis. Just for good measure, he went with Python 3 for the project. Because of that, he did have to spend a few hours porting Py65.

The port to Python 3 might have been easier for him due to his experience with the changes in the I/O system -- the topic of his Mastering Python 3 I/O tutorial. While the first revision of his port only took 15-20 minutes, he says “I don't want to give anyone the impression that they can just take some arbitrary library, run it through 2to3, and have it working over their coffee break. You really have to understand Python 3's I/O model and know what you're doing.” Attending his tutorial would certainly help you in that area.

Dave’s tutorial double duty also involves a joint presentation with Brian Jones titled Cooking With Python 3. They plan to cover the new features, the differences, and their experiences in porting. The pair are also teaming up to write the third edition of the Python Cookbook, which is going to be all about Python3, expected to hit the shelves in late 2011.

Since all of his tutorials and talks are Python 3 based, I wanted to ask him some general questions about where Python 3 is. “I think that the adoption of Python 3.x is proceeding just fine,” he says. He mentions the porting of NumPy as work “that will pave the way for others to start playing with [Python 3] and porting other packages.” On the whole, after mentioning that wide scale adoption was estimated to be around five years, he says it’s still too early to make a judgement on it.

However, he says “I do think that Python 3 presents developers with many possibilities to create new libraries and packages.” Additionally, “if you're going to port old code, it's a good opportunity to clean it up (since Python 3 breaks everything anyways, you can use it as excuse to get rid of all of those deprecated features that you're keeping around for backwards compatibility).”

He’s no stranger to Python conferences, getting his start in 1996 and attending most of the US conferences since then, plus PyCon UK in 2008. One of his trips was even last minute, deciding just days before that it’d be a fun time to attend one of the PyCons in Washington, D.C. Asked about his favorite part, he says “For me, the best part of the conference is the people. [...] It's a smart group and I always go home with ton of new ideas.”

We’re looking forward to all of the diabolical things he has planned and hope you are too. If you haven’t bought tickets, hurry up. A last minute trip probably will not work out for you like it did for Dave.

Comments

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 https://us.pycon.org/2018/ 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…