Python@TW: 會眾| IRC| Planet| 郵件列表| 聯絡我們
修訂版 30 和 31 的差異如下:
2007-02-24 10:28:04 修訂第 30 版
大小: 1740
編輯者: Thinker
說明:
2007-02-24 22:31:17 修訂第 31 版
大小: 2264
編輯者: yungyuc
說明:
這個顏色代表刪除的 這個顏色代表增加的
行號 8: 行號 8:
 * Sparse is better than dense. 寧可多寫幾行程式,不要省程式省到難懂。 --["yungyuc"]  * Sparse is better than dense. 寧可多寫幾行程式,不要省程式省到難懂。 -- ["yungyuc"]
行號 10: 行號 10:
 * Special cases aren't special enough to break the rules. 特例並不值得我們打破原則。 --["yungyuc"]  * Special cases aren't special enough to break the rules. 特例並不值得我們打破原則。 -- ["yungyuc"]
行號 12: 行號 12:
 * Errors should never pass silently. 千萬別讓錯誤靜靜的過去。--["alingo"] (不靜靜的放過任何錯誤)
 * Unless explicitly silenced. 除非是個顯而易見需要安靜對待的。--["alingo"] (除非你是故意的)
 * Errors should never pass silently. 千萬別讓錯誤靜靜的過去。-- ["alingo"] (不靜靜的放過任何錯誤)
 * Unless explicitly silenced. 除非是個顯而易見需要安靜對待的。-- ["alingo"] (除非你是故意的)
行號 15: 行號 15:
 * 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!
 * There should be one-- and preferably only one --obvious way to do it. 事情要有一種明顯的作法,最好也只有一種, -- ["yungyuc"]
 * Although that way may not be obvious at first unless you're Dutch. 雖然我們這些不是荷蘭人的人,一開始可能看不出來。 -- ["yungyuc"]
 * Now is better than never. 現在開始,強過不作, -- ["yungyuc"]
 * Although never is often better than *right* now. 雖然有時候不處理比*馬上*處理更好。 -- ["yungyuc"] (這兩句怪怪的? -- ["yungyuc"])
 * If the implementation is hard to explain, it's a bad idea. 不好解釋的實作方式,就不是好方式。 -- ["yungyuc"]
 * If the implementation is easy to explain, it may be a good idea. 容易解釋的實作方法,說不定是好方式。 -- ["yungyuc"]
 * Namespaces are one honking great idea -- let's do more of those! 命名空間是個頂呱呱的點子 -- 儘量用! -- ["yungyuc"]
  • [http://www.python.org/dev/peps/pep-0020/ PEP 20 ] The Zen of Python, by Tim Peters ([:PotPeople:POT眾]集體翻譯) -- 一人認領一句吧 :)

  • Beautiful is better than ugly. 美優於醜。 -- ["timchen119"]
  • Explicit is better than implicit. 顯明好過隱晦。 -- ["yungyuc"]
  • Simple is better than complex. 簡為上,繁複次之。 -- ["Thinker"]
  • Complex is better than complicated. 晦澀為下。 -- ["Thinker"]
  • Flat is better than nested. 平順善於巢雜。 -- ["keitheis"]
  • Sparse is better than dense. 寧可多寫幾行程式,不要省程式省到難懂。 -- ["yungyuc"]
  • Readability counts. 善兮,村姑可讀。 -- ["Thinker"] (應該同上句一起翻譯) (寧散不為短巧,村婦可讀)
  • Special cases aren't special enough to break the rules. 特例並不值得我們打破原則。 -- ["yungyuc"]
  • Although practicality beats purity. 雖然,理想終究不敵現實。 -- ["Thinker"]
  • Errors should never pass silently. 千萬別讓錯誤靜靜的過去。-- ["alingo"] (不靜靜的放過任何錯誤)
  • Unless explicitly silenced. 除非是個顯而易見需要安靜對待的。-- ["alingo"] (除非你是故意的)
  • In the face of ambiguity, refuse the temptation to guess. 隱者,晦者。不臆,不筮。 -- ["Thinker"]
  • There should be one-- and preferably only one --obvious way to do it. 事情要有一種明顯的作法,最好也只有一種, -- ["yungyuc"]
  • Although that way may not be obvious at first unless you're Dutch. 雖然我們這些不是荷蘭人的人,一開始可能看不出來。 -- ["yungyuc"]
  • Now is better than never. 現在開始,強過不作, -- ["yungyuc"]
  • Although never is often better than *right* now. 雖然有時候不處理比*馬上*處理更好。 -- ["yungyuc"] (這兩句怪怪的? -- ["yungyuc"])
  • If the implementation is hard to explain, it's a bad idea. 不好解釋的實作方式,就不是好方式。 -- ["yungyuc"]
  • If the implementation is easy to explain, it may be a good idea. 容易解釋的實作方法,說不定是好方式。 -- ["yungyuc"]
  • Namespaces are one honking great idea -- let's do more of those! 命名空間是個頂呱呱的點子 -- 儘量用! -- ["yungyuc"]

The Zen Of Python (上次是 ZoomQuiet 在 2010-04-08 09:57:40 編輯的)