[Python-Dev] None as a keyword / class methods

Jeremy Hylton jeremy-home@cnri.reston.va.us
Thu, 23 Mar 2000 15:55:25 -0500 (EST)

>>>>> "GVW" == gvwilson  <gvwilson@nevex.com> writes:

  GVW> To quote the immortal Jeremy Hylton:

  GVW>     Pythonic design rules #2: 
  GVW>             Explicit is better than implicit.

I wish I could take credit for that :-).  Tim Peters posted a list of
20 Pythonic theses to comp.lang.python under the title "The Python
Way."  I'll collect them all here in hopes of future readers mistaking
me for Tim again <wink>.

     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! 
for the full post.

to-be-immortal-i'd-need-to-be-a-bot-ly y'rs