Skip to main content

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 useful.

raise_(TypeError("Wrong datatype!"))

When you do have exceptions, you often want to handle them and we can even do this in expressions now. Maybe we just want to report the error. The try_ function takes keywords for except_, else_, and finally_ callbacks. All take exception type, exception, and traceback arguments, with else_ and _finally also taking first arguments as the result of the attempted callable.

try_(some_func, except_=lambda e,et,tb:print_(et, ':', e))

Errors also can come from failed assertions.

assert_(lambda: True == False)

Loops are also supported. for_ is mostly like map, but it also takes an else_ argument which is called with the last value from the iterator. while_ takes a condition callable, either a for_each callable or an iterator. The condition is given the result of the last loop.

for_("abc", print_, lambda i: print_("done"))

while_(lambda last:last<99, xrange(100), lambda_ i: print_("done"))

Finally, some simple ones:

pass_(10, foo="a") # returns ((10,), {'foo': 'a'})

exec_("a = b", globals(), locals())

I don't recommend using this a whole lot, but in the cases its useful, enjoy.

Comments

bobuk said…
Wow! Nice-nice-nice!

But in if_ you need to rename callbacks from cb_true to then_ and from cb_false to else_!

Popular posts from this blog

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…

On Pruning Your Passions

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

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. The only re…