的编码原则

图片 1

C:JS>python
Python 3.6.0 (v3.6.0:41df79263a11, Dec 23 2016, 08:06:12) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import this

执行命令:import this,就可以看到 Tim Peters 写的 Python 编码原则,原文如下:

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.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!

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.
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!

翻译如下:

翻译

  • 优美胜于丑陋。(代码应该写的漂亮而优雅。)
  • 清晰胜于晦涩。(清晰的代码更容易维护。)
  • 简洁胜于复杂。
  • 复杂胜于混杂。
  • 扁平胜于嵌套。
  • 间隔胜于紧凑。
  • 可读性很重要。(即便是复杂的代码, 也要让它易于理解。 特别是涉及到复杂代码时, 一定要为这些代码编写有益的注释。)
  • 即便是特例,也不能以特例之名,破坏这些规则。
  • 实用胜于纯粹。
  • 不要放过错误,除非有明确要求。
  • 当存在多种可能时,不要猜测,而是要尽力找出一种方案,而且最好是一种显而易见的解决方案。有时候,这并不容易,除非你是 Python 之父 Guido(因为 Guido 是荷兰人)。
  • 马上做也许好过从未开始,但不假思索地做有时候还不如不做 。
  • 一个好的实现方案,也是容易描述的,反之亦然。
  • 命名空间是一个值得大力倡导的概念。

Python之禅
  赖勇浩翻译
  
  优美胜于丑陋(Python 以编写优美的代码为目标)
  明了胜于晦涩(优美的代码应当是明了的,命名规范,风格相似)
  简洁胜于复杂(优美的代码应当是简洁的,不要有复杂的内部实现)
  复杂胜于凌乱(如果复杂不可避免,那代码间也不能有难懂的关系,要保持接口简洁)
  扁平胜于嵌套(优美的代码应当是扁平的,不能有太多的嵌套)
  间隔胜于紧凑(优美的代码有适当的间隔,不要奢望一行代码解决问题)
  可读性很重要(优美的代码是可读的)
  即便假借特例的实用性之名,也不可违背这些规则(这些规则至高无上)
  不要包容所有错误,除非你确定需要这样做(精准地捕获异常,不写 except:pass 风格的代码)
  当存在多种可能,不要尝试去猜测
  而是尽量找一种,最好是唯一一种明显的解决方案(如果不确定,就用穷举法)
  虽然这并不容易,因为你不是 Python 之父(这里的 Dutch 是指 Guido )
  做也许好过不做,但不假思索就动手还不如不做(动手之前要细思量)
  如果你无法向人描述你的方案,那肯定不是一个好方案;反之亦然(方案测评标准)
  命名空间是一种绝妙的理念,我们应当多加利用(倡导与号召)

The Zen of Python,
  蛇宗三字经
  
  作者: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.
  虽不至,向往之
  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!
  每师出,多有名

本文由365bet体育在线官网发布于网络工程,转载请注明出处:的编码原则

TAG标签:
Ctrl+D 将本页面保存为书签,全面了解最新资讯,方便快捷。