from this import *

The Zen of Python, by Tim Peters

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!

>>7
HAHAHAHAHAHAHAHHAHAHAHAAHAHAAAA!!!
you think your tough huh?
one word THE FORCED INDENTATION OF CODE.
i have taken out two mission critical applications at the same time in less than 5 seconds i have been training for 3 years.
also enterprise grade best practices.
your compiler might be bigger than me,but i know mine is smarter and quicker.
my compiler is 130 kb pure lean code.
one keystroke and i'll overflow your buffers.
your the one whose a nerd.i can optimize CFLAGS anytime i want you probably haven't ever touched CFLAGS before.
you probably have sex with your computer.
you don't even know me,and you don't want to.
you'll be lucky if your even worth my attention one look at my code and you'll dissappear forever.
though i'd be hapy to humiliate you in front of all your friends.
btw IM the expertest.
i have worked in maine, new hampshire, new york,utah, colorado,florida,bahamas.
never indented my code!
im undefeated in competitive obfuscation of code.
im on my way to IOCCC.
go ahead and come step anytime you want.b*tch