Skip to main content

Utilizing Python's Assert Statements for Compile-Time Checks

Some recent discussions around the 'net have been tossing around the ideas about static typing in python, briding static and dynamic typing in C++-like languages, and similar concepts of making static-typing more dynamic or dynamic languages more optimized in static-typing ways. Particularly, I was sparked by Michael Feather's "Set of Tests" article. There are different ways we might look into bringing those concepts to Python, and I rolled a few of them around in my head. My final mental landing was "Can we utilize the assert statement to inform the compiler about these tests that are absolute?". Of course, you probably can see how this is a lot like what assert does now, with the only difference being between run-time and compile-time being the target of the rules. This leads us to looking for where an assert could be compile-time verified and then used to optimize code. The most basic compile-time assert I can think of us "assert builtin is builtin", which would be a contract that the name 'builtin' will continue to be bound to the default builtin object, and won't be changed. This means we can do "assert isinstance is isinstance" and the compiler can make assumptions it could not before: that when it sees the name isinstance, it knows exactly what it is before runtime. This opens up other expressions that use these known names and promise other things to the compiler. We could do things like "assert isinstance(l, sequence)" or "assert len(l)==3", which would create a pair of contracts that l was some kind of 3 element sequence, and the compiler could make it a tuple for optimization.

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be u

How To use Sphinx Autodoc on ReadTheDocs with a Django application

Sphinx is awesome for writing documentation. ReadTheDocs is awesome for hosting it. Autodocs are great for covering your entire API easily. Django is a great framework that makes my job easier. Between these four things is an interaction that only brought me pain, however. I'm here to help the next dev avoid this. Autodocs works by importing your modules and walking over the classes and functions to build documentation out of the existing docstrings. It can be used to generate complete API docs quickly and keep them in sync with the libraries existing docstrings, so you won't get conflicts between your docs and your code. Fantastic. This creates a problem when used with Django applications, where many things cannot be imported unless a valid settings module can be found. This can prevent a hurdle in some situations, and requires a little boilerplate to get working properly with Sphinx. It require a little extra to get working on ReadTheDocs. What makes this particularly h