1 Beautiful is better than ugly. 2 # 优美胜于丑陋(Python以编写优美的代码为目标) 3 Explicit is better than implicit. 4 # 明了胜于晦涩(优美的代码应当是明了的,命名规范,风格相似) 5 Simple is better than complex. 6 # 简洁胜于复杂(优美的代码应当是简洁的,不要有复杂的内部实现) 7 Complex is better than complicated. 8 # 复杂胜于凌乱(如果复杂不可避免,那代码间也不能有难懂的关系,要保持接口简洁) 9 Flat is better than nested. 10 # 扁平胜于嵌套(优美的代码应当是扁平的,不能有太多的嵌套) 11 Sparse is better than dense. 12 # 间隔胜于紧凑(优美的代码有适当的间隔,不要奢望一行代码解决问题) 13 Readability counts. 14 # 可读性很重要(优美的代码是可读的) 15 Special cases aren't special enough to break the rules. 16 Although practicality beats purity. 17 # 即便假借特例的实用性之名,也不可违背这些规则(这些规则至高无上) 18 Errors should never pass silently. 19 Unless explicitly silenced. 20 # 不要包容所有错误,除非你确定需要这样做(精准地捕获异常,不写except:pass风格的代码) 21 In the face of ambiguity, refuse the temptation to guess. 22 # 当存在多种可能,不要尝试去猜测 23 There should be one-- and preferably only one --obvious way to do it. 24 # 而是尽量找一种,最好是唯一一种明显的解决方案(如果不确定,就用穷举法) 25 Although that way may not be obvious at first unless you're Dutch. 26 # 虽然这并不容易,因为你不是 Python 之父(这里的Dutch是指Guido) 27 Now is better than never. 28 Although never is often better than *right* now. 29 # 做也许好过不做,但不假思索就动手还不如不做(动手之前要细思量) 30 If the implementation is hard to explain, it's a bad idea. 31 If the implementation is easy to explain, it may be a good idea. 32 # 如果你无法向人描述你的方案,那肯定不是一个好方案;反之亦然(方案测评标准) 33 Namespaces are one honking great idea -- let's do more of those! 34 # 命名空间是一种绝妙的理念,我们应当多加利用(倡导与号召)