Skip to main content

PyCon: Opening the Flask

Opening the Flask

The talk was by Armin Ronacher, one of the authors of Flask.

Flask started as an elaborate April Fool's joke.

The guys who did Flask did a lot of cool stuff before doing Flask, such as Jinja2.

Flask was originally Jinja2, Werkzeug, and some glue code cleverly embedded in a single file download.

Marketing beats quality.

Originally, they didn't do any testing or any code review. That's changed.

They wanted to restart with good docs and good tests. They documentation and tests are pretty good these days.

The name "Flask" is a play on another framework, "Bottle".

Flask is still based on Werkzeug and Jinja2.

Flask can use Blinker as a signalling system (?).

Flask is about 800 lines of code, 1500 lines of tests, and 200 A4-sized pages of documentation.

There are lots of extensions.

Flask uses decorator-based routes, but there are other options.

Flask supports URL routing as well as URL generation.

Jinja2 uses template inheritance.

They use context locals to make writing apps simper. Armin suggests that you might as well embrace context locals--you'll end up needing them anyway.

Armin is very against import-time side effects.

Flask is in favor of explicit application setup. For Flask, this has occasionally led to circular imports that they had to find workarounds for.

WSGI middleware works with Flask.

Flask has several advantages over Bottle.

You can override various aspects of how Flask works. For instance, you can use the "@app.before_request" and "@app.after_request" decorators.

They make use of lots of extensions.

Flask has a goal of keeping the core very small.

You can use other templating engines if you want, but Jinja2 will always be a dependency just in case any extensions need it.

Documentation matters.

Communication matters. It's very easy to submit issues to Flask. You don't even need to create an account.

It's important to keep committing to projects otherwise the project looks dead.

Consistency matters.

It's important that even the documentation be beautiful.

Flask uses Sphinx for documentation.

Armin didn't have a strong rule of thumb for when you should use Flask vs. Pyramid. Neither the Flask guys nor the Pyramid guys are overly religious about their frameworks.

The audience turnout was about the same for both the Flask and Pyramid talks.

The Flask guys are thinking about redoing the code for reverse routing.

Comments

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p