October 27, 2011

I saw this linked to by Scot Hacker and then tracked it down to the index of all Python Enhancement Proposals.

As a set of general rules it’s a pretty good one!

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!

Writing


Previous post Grandmother’s Traditional Rhyme Photo by Mike Bitzenhofer When reading Peter Ackroyd’s Biography of London I was reminded of a rhyme my grandmother used to recite to me. In the Next post Slide Film It’s not often that I have a chance to try a film that’s new to me but I recently bought some Kodak E100VS film - a film that Kodak claims provides