Skip to main content

PyCon: Code Generation in Python: Dismantling Jinja

See the website.

See also

Is eval evil? How does it impact security and performance?

Use repr to get something safe to pass to eval for a given type.

Eval code in a different namespace to keep namespaces clean.

Using code generation results in faster code than writing a custom interpreter in Python.

Here is a little "Eval 101".

Here is how to compile a string to a code object:
code = compile('a = 1 + 2', '', 'exec')
ns = {}
exec code in ns # exec code, ns in Python 3.
ns['a'] == 3
In Python 2.3 or later, use "ast.parse('a = 1 + 2')", and then pass the result to the compile function.

You can modify the ast (abstract syntax tree).

You can assign line numbers.

You don't have to pass strings to eval and exec. You can handle the compilation to bytecode explicitly. You can also execute the code in an explicit namespace.

Jinja mostly has Python semantics, but not exactly. It uses different scoping rules.

Lexer -> Parser -> Identifier Analyzer -> Code Generator -> Python Source -> Bytecode -> Runtime

Everything before the runtime can be done ahead of time and cached.

Because WSGI uses generators, Jinja also uses generators for output.

You can run untrusted template code with Jinja. They restrict what the Python can do. (I'm skeptical.)

They have automatic escaping.

In the art of code generation, you must think in terms of low level vs. high level.

(I got a little confused at this point about whether Jinja generated bytecode, ASTs, or Python source. Later in the talk, it seemed like he was saying that Jinja always generated Python code because it was the only workable option at the time.)

Using the ast module only became an option later.

He thought about generating bytecode. However, that doesn't work on Google App Engine. Furthermore, it was too implementation specific.

Using the ast module is more limited. However, it's easier to debug. Furthermore, it does not segfault the interpreter (at least starting in Python 2.7).

Using pure source code generation always works. However, it's very limited, and it's hard to debug without hacks.

The ast module is much better.

Jinja is way faster than Django templates.

Code running in a function is faster than running at global scope because local variable lookup is faster.

They keep track of identifiers and track them through the source code.

The context object in Jinja2 is a data source (read only). In Django, it's a data store (read write).

What happens in the include stays in the include. An include can't change a variable in an outer scope.

Jinja looks at your template and generates more complicated code if your code needs more complicated code.

{% for item in sequence %} creates item in a context that's only valid in the for loop.

Jinja used manual code generation because it was the only option. AST compilation is new in Python 2.6.

A Markup object wraps a string, but has autoescaping. It uses operator overloading. Jinja can do some escaping at compile time.

Undefined variables in Jinja are replaced by undefined objects so that they print out as empty strings. However, doing an attribute lookup on such an object raises an exception.

He would use the ast module if he had to do it all over again.


Popular posts from this blog

Drawing Sierpinski's Triangle in Minecraft Using Python

In his keynote at PyCon, Eben Upton, the Executive Director of the Rasberry Pi Foundation, mentioned that not only has Minecraft been ported to the Rasberry Pi, but you can even control it with Python. Since four of my kids are avid Minecraft fans, I figured this might be a good time to teach them to program using Python. So I started yesterday with the goal of programming something cool for Minecraft and then showing it off at the San Francisco Python Meetup in the evening.

The first problem that I faced was that I didn't have a Rasberry Pi. You can't hack Minecraft by just installing the Minecraft client. Speaking of which, I didn't have the Minecraft client installed either ;) My kids always play it on their Nexus 7s. I found an open source Minecraft server called Bukkit that "provides the means to extend the popular Minecraft multiplayer server." Then I found a plugin called RaspberryJuice that implements a subset of the Minecraft Pi modding API for Bukkit s…

Apple: iPad and Emacs

Someone asked my boss's buddy Art Medlar if he was going to buy an iPad. He said, "I figure as soon as it runs Emacs, that will be the sign to buy." I think he was just trying to be funny, but his statement is actually fairly profound.

It's well known that submitting iPhone and iPad applications for sale on Apple's store is a huge pain--even if they're free and open source. Apple is acting as a gatekeeper for what is and isn't allowed on your device. I heard that Apple would never allow a scripting language to be installed on your iPad because it would allow end users to run code that they hadn't verified. (I don't have a reference for this, but if you do, please post it below.) Emacs is mostly written in Emacs Lisp. Per Apple's policy, I don't think it'll ever be possible to run Emacs on the iPad.

Emacs was written by Richard Stallman, and it practically defines the Free Software movement (in a manner of speaking at least). Stal…

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, 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." I bet it&…