记录一下python的编码规则和编码之禅

0.python之禅

>>> import this
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!

# 翻译
优美胜于丑陋
明了胜于晦涩
简单胜于复杂
复杂胜于凌乱
扁平胜于嵌套
间隔胜于紧凑
可读性至关重要
即使假借特例的实用性之名，也不可违背这些原则

不要包容所有错误，除非你确定需要这样做

当存在多种可能，不要去猜测
而是尽量找一种，最好是唯一一种明显的解决方案
虽然这样并不容易，因为你不是guido

做也许好过不做，但不假思索就动手还是不如不做

如果你无法向人描述你的方案，那肯定不是一个好方案，反之亦然

命名空间是一种绝妙的理念，应当多加利用

1. 编码规定

1.1 代码布局

1. 缩进：4个空格

   在需要折行的情况下，需要保持元素对齐。

2. Tab和空格不可混用。

3. 每行长度建议不超过79个字符，尽量不要折行

4. 换行在二元操作符之后

5. 类或顶级方法之间上下间隔两行，类内部的方法上下间隔一行

6. 每个import单独一行

7. 库的引用：

   1. 标准库
   2. 相关第三方库
   3. 本项目中其它模块的引用

   避免使用通配符引用，以免污染命名空间。

8. 模块级别的双下划线命名

"""This is model"""from __future__ import xxxx__all__ = [1,2,3]__version__ = '0.1'__author__ = 'Vanre'

8. 字符串引号：一般选择一种持续引用（建议双引号）