python哲学

import this

The Zen of Python, by Tim Peters
# python的设计哲学, 作者：Tim Peters

Beautiful is better than ugly.
# 优雅胜于丑陋（Python 以编写优美的代码为目标）

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.
# 错误不可置之不理，除非你确定需要这样做（精准地捕获异常，不写 except:pass 风格的代码）

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之父（这里的 Dutch 是指 Guido ）

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!
# 就像命名空间就是一个绝妙的想法，应当多加利用