Python哲学之import this,诠释代码之美

Python虽为简洁但是也很挑剔,它比较注重格式,为了更好地去搞清楚它的写法,在Python中有一个彩蛋,import this,如果我们真的明白了这个彩蛋的含义,我想会对我们的写法格式有很大的帮助
在这里插入图片描述

  1. Beautiful is better than ugly.
  • 优美胜于丑陋(Python以编写优美的代码为目标)
  1. Explicit is better than implicit.
  • 明了胜于晦涩(优美的代码应当是明了的,命名规范,风格相似)
  1. Simple is better than complex.
  • 简洁胜于复杂(优美的代码应当是简洁的,不要有复杂的内部实现)
  1. Complex is better than complicated.
  • 复杂胜于凌乱(如果复杂不可避免,那代码间也要简洁明了,要保持接口简洁)
  1. Flat is better than nested.
  • 扁平胜于嵌套(优美的代码应该是扁平的,不能有太多的嵌套)
  1. Sparse is better than dense.
  • 间隔胜于紧凑(优美的代码有适当的间隔,不要奢望一行代码解决问题,注意缩进)
  1. Readability counts.
  • 可读性很重要(优美的代码是可读的,看上去是很完美的)
  1. Special cases aren’t special enough to break the rules.
  • 即便假借特例的实用性之名,也不可违背这些规则(这些规则至高无上)
  1. Although practicality beats purity.
  • 虽然实用性次纯度
  1. Errors should never pass silently.
  • 不要包容所有错误
  1. Unless explicitly silenced.
  • 除非你确定需要这样做(精准地捕获异常)
  1. In the face of ambiguity, refuse the temptation to guess.
  • 当存在多种可能,不要尝试去猜测
  1. There should be one-- and preferably only one --obvious way to do it.
  • 而是尽量找一种,最好是唯一一种明显的解决方案
  1. Although that way may not be obvious at first unless you’re Dutch.
  • 虽然这并不容易,因为你不是 Python 之父(这里的 Dutch 是指 Guido )
  1. Now is better than never.
  • 做也许好过不做(动手之前要细思考,有目标的去做)
  1. Although never is often better than right now.
  • 虽然过去从未比现在好。
  1. If the implementation is hard to explain, it’s a bad idea.
  • 如果你无法向人描述你的方案,那肯定不是一个好方案(方案测评标准)
  1. If the implementation is easy to explain, it may be a good idea.
  • 如果你很容易向人描述你的方案,那肯定是一个好方案
  1. Namespaces are one honking great idea – let’s do more of those!
  • 命名空间是一种绝妙的理念,我们应当多加利用(倡导与号召)

猜你喜欢

转载自blog.csdn.net/qq_45096273/article/details/107573321
今日推荐