import this
The Zen of Python, by Tim Peters
##01-强调代码简洁
Beautiful is better than ugly.
##02- 明了胜于晦涩（优美的代码应当是明了的，命名规范，风格相似）
Explicit is better than implicit.
##03-简洁优于复杂
Simple is better than complex.
##04-复杂优于凌乱（如果复杂不可避免，那代码间也不能有难懂的关系，要保持接口简洁）
Complex is better than complicated.
##06-扁平优于嵌套（优美的代码应当是扁平的，不能有太多的嵌套）
Flat is better than nested.
##07-间隔优于紧凑（优美的代码有适当的间隔，不要奢望一行代码解决问题）
Sparse is better than dense.
##08-尽量考虑可读易于理解
Readability counts.
##09-不能为例外违背规则规则
#### 尽管我们在纯粹性和实用性之间是倾向实用性的。
Special cases aren't special enough to break the rules.
Although practicality beats purity.
##10-错误决不能安静错过
#### 除非明确的说明了是静静地Pass。
Errors should never pass silently.
Unless explicitly silenced.
##11-模棱两可面前拒绝陷入猜测
#### 而是尽量找一种，最好是唯一一种明显的解决方案（如果不确定，就用穷举法）
#### 虽然这并不容易，因为你不是 Python 之父（这里的 Dutch 是指 Guido ）
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.
##12-做也许好过不做，但不假思索就动手还不如不做（动手之前要细思量）
Now is better than never.
Although never is often better than right now.
##13-如果你无法向人描述你的方案，那肯定不是一个好方案；反之亦然（方案测评标准）
#### 如果一个实现很难解释清楚，说明实现的idea有问题。
#### 如果一个实现很容易解释清楚，那可能是个好的实现idea。
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.
##14-命名空间是一种绝妙的理念，我们应当多加利用（倡导与号召）
Namespaces are one honking great idea -- let's do more of those!