Simple is better than complex.

Errors should never pass silently.

Errors should never pass silently.

Beautiful is better than ugly.

Now is better than never.

Namespaces are one honking great idea -- let's do more of those!

Namespaces are one honking great idea -- let's do more of those!

Complex is better than complicated.

Complex is better than complicated.

Explicit is better than implicit.

Flat is better than nested.

'for Guido to fill in'ORit's an opportunity for people to provide their own addition.https://stackoverflow.com/questions/4504487/the-zen-of-python-distils-the-guiding-principles-for-python-into-20-aphorisms-bu#24814971

20th principle

Unless explicitly silenced.

Although never is often better than *right* now.

Although never is often better than *right* now.

If the implementation is easy to explain, it may be a good idea.

If the implementation is easy to explain, it may be a good idea.

Special cases aren't special enough to break the rules.

Special cases aren't special enough to break the rules.

Although that way may not be obvious at first unless you're Dutch.

Although that way may not be obvious at first unless you're Dutch.

In the face of ambiguity, refuse the temptation to guess.

In the face of ambiguity, refuse the temptation to guess.

There should be one-- and preferably only one --obvious way to do it.

There should be one-- and preferably only one --obvious way to do it.

Long time Pythoneer Tim Peters succinctly channels the BDFL’s guiding principles for Python’s design into 20 aphorisms, only 19 of which have been written down.https://peps.python.org/pep-0020/

import this

Sparse is better than dense.

If the implementation is hard to explain, it's a bad idea.

If the implementation is hard to explain, it's a bad idea.

Although practicality beats purity.

Special cases aren't special enough to break the rules.

Similar ideas to Special cases aren't special enough to break the rules.

10. Follow the rules, and then unfollow the rules

Special Cases

Life Rules