Differences between revisions 8 and 19 (spanning 11 versions)
Revision 8 as of 2005-08-07 04:07:15
Size: 1224
Editor: limodou
Comment:
Revision 19 as of 2012-11-09 00:48:08
Size: 575
Editor: ZoomQuiet
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
= 禅 =
 * 缘起: [[http://www.python.org/peps/pep-0020.html|pep-0020]] -- 禅在Python.org
  [[http://python.cn/pipermail/python-chinese/2005-February/008111.html|jian wang wangjian5748 at sohu.com 先译]]
 * 解释: PythonZen/ExPlain
 * 例程: [[http://artifex.org/~hblanks/talks/2011/pep20_by_example.html|]]
Line 6: Line 11:
::-- ZoomQuiet [[[DateTime(2005-02-18T02:58:19Z)]]] ||[[/PyZenZhTry|译文]]||原文||
||<^><<Include(/PyZenZhTry,,from="^##startInc$",to="^##endInc$")>>||<^ 50%><<Include(/PythonZenEn)>>||
Line 8: Line 14:
= 禅 =
 * [http://www.python.org/peps/pep-0020.html pep-0020] -- 禅在Python.org
  * [http://python.cn/pipermail/python-chinese/2005-February/008111.html jian wang wangjian5748 at sohu.com 先译]

解释: PythonZen/ExPlain

||译文||原文||
||<^>[[Include(/PythonZenZh)]]||<^>[[Include(/PythonZenEn)]]||

我也翻译了一下 译文 ["limodou"]

{{{
优美胜过丑陋
明确胜过含蓄
简单胜过复杂
复杂胜过难懂
扁平胜过嵌套
稀疏胜过密集
易读亦有价
尽管实用会击败纯洁
特例也不能特殊到打破规则
除非明确地使其沉默
错误永远不应默默地溜掉
面对着不确定,要拒绝猜测的诱惑
应该有一个--宁肯只有一个--明显的实现方法
也许这个方法开始不是很明显,除非你是荷兰人
尽管不做通常好过立刻做
但现在做也要胜过不去做
如果实现很难解释,那它就是一个坏想法
如果实现容易解释,那它可能就是一个好想法
名字空间是一个响亮的出色想法--就让我们多用用它们

-- Tim Peters
-- 译:limodou
}}}
::-- ZoomQuiet [<<DateTime(2005-02-18T02:58:19Z)>>]

Zen of Python -- 蟒之禅!

译文

原文

收集网络中的翻译版本,排名不分先后

  1. 禅译之ZoomQuiet版

  2. 禅译之Limodou版

  3. 禅译之Shhgs版

  4. 赖勇浩《Python之禅》的翻译和解释 -

  5. 禅译之曹星明版

  6. 禅译之Azrael版

The Zen of 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!

-- by Tim Peters

::-- ZoomQuiet [2005-02-18 02:58:19]

PythonZen (last edited 2012-11-09 00:48:08 by ZoomQuiet)