Python之禪 最早由Tim Peters在Python郵件列表中發表，它包含了影響Python程式語言設計的19條軟體編寫原則。
在最初及後來的一些版本中，一共包含20條，其中第20條是「這一條留空請 Guido 來填寫」。
這留空的一條從未公布也可能並不存在。這些文本屬於公共領域。 [維基百科]

執行import this，可以看到以下的輸出：

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
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.
雖然你一開始的方法不一定是最好的，除非你是荷蘭人
解決一個問題的方法可能會有很多種，但在 Python 中，只選擇最明顯的那一個

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!
命名空間是個絕佳機制, 要充分利用