Scribd
Upload
744 views1 page

Zen of Python (Poster)

This document contains the "Zen of Python" which provides guiding principles for Python design. It favors readable, simple and explicit code over complex code and emphasizes there should be obvious ways to do things while avoiding ambiguity. Special cases should not override general rules and practicality is important though purity has value. Errors should not pass silently and namespaces are a useful mechanism.

Uploaded by

Raphael Rissato
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
744 views1 page

Zen of Python (Poster)

This document contains the "Zen of Python" which provides guiding principles for Python design. It favors readable, simple and explicit code over complex code and emphasizes there should be obvious ways to do things while avoiding ambiguity. Special cases should not override general rules and practicality is important though purity has value. Errors should not pass silently and namespaces are a useful mechanism.

Uploaded by

Raphael Rissato
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

import this

“““The Zen of Python, by Tim Peters”””

1 Beautiful is better than ugly.


2 Explicit is better than impl..
3 Simple is better than c0mplℇ".
4 Complex is better than c0mp|1c@ted.
5 Flat is better than nested.
6 S p a r s e is better than dense.
7 Readability counts.
8 Special cases aren't special enough to break the rules.
9 Although practicality beats purity.
10 raise PythonicError(“Errors should never pass silently.”)
11 # Unless explicitly silenced.
12 In the face of ambiguity, refuse the temptation to guess.
13 There should be one-- and preferably only one --obvious way to do it.
14 # Although that way may not be obvious at first unless you're Dutch.
15 Now is better than... never.
16 Although never is often better than right now.
17 If the implementation is hard to explain, it's a bad idea.
18 If the implementation is easy to explain, it may be a good idea.
19 Namespaces are one honking great idea -- let's do more of those!

You might also like