The Zen of Python

Beautiful is better than ugly – be consistent.
Complex is better than complicated – use existing libraries.
Simple is better than complex – keep it simple and stupid (KISS).
Flat is better than nested – avoid nested ifs.
Explicit is better than implicit – be clear.
Sparse is better than dense – separate code into modules.
Readability counts – indenting for easy readability.
Special cases aren’t special enough to break the rules – everything is an object.
Errors should never pass silently – good exception handler.
Although practicality beats purity - if required, break the rules.
Unless explicitly silenced – error logging and traceability.
In ambiguity, refuse the temptation to guess – Python syntax is simpler; however, many times we might take a longer time to decipher it.
Although that way may not be obvious at first unless you’re Dutch – there is not only one of way of achieving something.
There should be preferably only one obvious way to do it – use existing libraries.
If the implementation is hard to explain, it’s a bad idea – if you can’t explain in simple terms then you don’t understand it well enough.
Now is better than never – there are quick/dirty ways to get the job done rather than trying too much to optimize.
Although never is often better than *right* now – although there is a quick/dirty way, don’t head in the path that will not allow a graceful way back.
Namespaces are one honking great idea, so let’s do more of those! – be specific.
If the implementation is easy to explain, it may be a good idea – simplicity.