说说 Python 的编码原则

版权声明:如果喜欢,就点个赞呗 O(∩_∩)O~ https://blog.csdn.net/deniro_li/article/details/86763693

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

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 是荷兰人)。
  • 马上做也许好过从未开始,但不假思索地做有时候还不如不做(三思而后行)  。
  • 一个好的实现方案,也是容易描述的,反之亦然。
  • 命名空间是一个值得大力倡导的概念。

猜你喜欢

转载自blog.csdn.net/deniro_li/article/details/86763693