Skip to main content

PyCon 2011: Interview with Armin Ronacher - “Opening the Flask”

By Brian Curtin

It’s not often that “April Fools” jokes go past the joke stage, especially in the Python community. PEP-3117 didn’t make it, and Uncle Barry’s PEP-401 takeover hasn’t yet occurred. However, we’re still seeing the work of an April 1, 2010 joke in the form of Flask, Armin Ronacher’s micro-framework.

For a fake project, it certainly got a lot of attention. Within days after announcing the joke Denied micro-framework, 10,000 people downloaded the fake screencast, 50,000 people viewed the website, and the project had 50 followers and 6 forks on github. “The great thing about being part of a vibrant open source community like the Python one is that you learn a lot more about people and yourself than you do about the project itself,” said Ronacher. The joke was an exercise in project judgment, and people seemed to like the idea and bought into it right away, many without noticing the quality of the code or lack of documentation, but the flashiness of a screencast.

His talk “Opening the Flask” hopes to give an inside look and draw some conclusions from the year of work to make the real project what it is today. When asked what turned the joke into reality, he says, “My original frustration that lead to the April Fool's joke framework was the fact that some frameworks chose to re-implement WSGI […] just to be able to claim ‘no dependencies’.” From there, he decided it was worth a shot at creating a real framework based on his Werkzeug and Jinja2 projects. After all, people seemed to like the joke micro-framework idea, and a year later, people love it, so he’s doing something right.

Extensions are one of the key topics of the talk, and Armin recently announced the 30th extension had been created by the community. Asked about his favorite extension, he says “I love relational databases and I adore the design and implementation of SQLAlchemy so I would say Flask-SQLAlchemy is the one I use the most.” Another of his favorites is Flask-Script, which is similar to django-management in the Flask world.

Armin is one of the younger Python hackers out there today, getting his start into development around 2002 by writing games at school using QBasic. After finding a Delphi book and ignoring most of the contents, he and a friend “wrote a horribly developed game called ‘be a bee’.” They ended up taking that game to the under-19 ARS Electronica festival in 2003 and won second prize.

He found Python by way of Gregor Lingl’s “Python fuer Kids”, then shortly joined the German Python Forum. After getting acquainted with Ubuntu, he spent time working with the ubuntuusers.de forum, which ended in the creation of the Pocoo project. “Having something to work for and a Python core developer on board (Georg Brandl joined the project very early) is a great way to learn the language.”

While this will be Armin’s first US Pycon, he’s been to EuroPython and a number of Django conferences, and he’s no stranger to speaking there. To him, one of the best parts of the conference is “talking to other developers in the hallways and sharing experiences.”

We’re looking forward to his talk in Atlanta - it should be a great time, and Flask is another great addition to the Python web ecosystem. Over the next few weeks, we will be posting more interviews with upcoming speakers, authors and others involved in Pycon 2011, so stay tuned - and get registered!

Comments

Popular posts from this blog

Hatchery Program Returns for 2019

PyCon is known around the world as the Python community’s premier event, attracting people from 39 countries. Outside of the main track of talks, PyCon is home to a growing number of events such as Young Coders, the Education Summit, Language Summit, Poster Session, and most recently the PyCon Charlas. The conference strives to be globally representative by promoting diversity and inclusion through these additional events and outreach programs. Our community works to approach these goals year on year. While we regularly receive requests to add events to PyCon, we have not had an established process for accepting and evaluating the community’s suggestions. By introducing the PyCon Hatchery Program in 2018, we took an initial step to introduce a long term process for evolving PyCon. What is our goal?We want to support our community and enable them to add events to PyCon that are important to our community. The long-term goals of this program are to support and grow sustainable programs th…

Pycon 2019 Call for Proposals is Open!

The time is upon us again! PyCon 2019’s Call for Proposals has officially opened for talks, tutorials, posters, education summit presentations, as well as the hatchery program PyCon Charlas. 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.

Please make note of important deadlines for submissions:
Tutorial proposals are due November 26, 2018.Talk, Charlas, Poster, and Education Summit proposals are due January 3, 2019.
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…

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…