23.py

#!/usr/bin/env python
#title: what is this module?
#hint1: it can't find it. this is an undocumented module.
#hint2: va gur snpr bs jung?' <- ROT13 -> 'in the face of what?'

##TODO: do you owe someone an apology? now it is a good time to
##tell him that you are sorry. Please show good manners although
##it has nothing to do with this level.

#From: Leopold Mozart <leopold.moz@pythonchallenge.com>
#Subject: Re: sorry
#Never mind that.
#Have you found my broken zip?
#md5: bbb8b499a0eef99b52c7f13f4e78c24b
#Can you believe what one mistake can lead to? 


	
Czech proverb


Gur Mra bs Clguba, ol Gvz Crgref
The Zen of Python, by Tim Peters		http://www.python.org/doc/Humor.html#zen

taher@borg:/usr/lib/python2.5$ grep -i "va gur snpr bs" *
this.py:Va gur snpr bs nzovthvgl, ershfr gur grzcgngvba gb thrff.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!