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
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!
相关文章
- 12-04from __future__ import absolute_import
- 12-04Xcode svn import项目 上传.a文件(静态库)
- 12-04from bs4 import BeautifulSoup 引入需要安装的文件和步骤
- 12-04在beautifulsoup安装的前提下,报如下错误cannot import name 'Beautifulsoup4' from 'bs4'的解决办法
- 12-04windows anaconda python3.7 import ssl,psycopg2报错
- 12-04Js 模块导入import的用法总结
- 12-04import uno 错误
- 12-04python3报错:import urllib2 ModuleNotFoundError
- 12-04import同目录的py文件 :ModuleNotFoundError: No module named 'pdf'
- 12-04关于“The import org.junit.jupiter cannot be resolved”出现错误