summaryrefslogtreecommitdiff
path: root/CODING
diff options
context:
space:
mode:
authordavemds <dave@gurumeditation.it>2013-03-30 14:17:52 +0100
committerdavemds <dave@gurumeditation.it>2013-03-30 14:17:52 +0100
commitf607d989a156d9500851229893712cc2538cc55e (patch)
tree40183f2322e7de3ee8207411c0c09e24458d343d /CODING
parent90a73380d6f149503e3ad451260acd3622d4ca9c (diff)
Python-EFL: The Zen of Python :)
Diffstat (limited to 'CODING')
-rw-r--r--CODING27
1 files changed, 27 insertions, 0 deletions
diff --git a/CODING b/CODING
index c390d1b..bcf1b41 100644
--- a/CODING
+++ b/CODING
@@ -8,6 +8,33 @@ Style
8 This makes a visual distinction between C and py code and don't confuse the 8 This makes a visual distinction between C and py code and don't confuse the
9 reader as "==" and "is" has different meaning in python. 9 reader as "==" and "is" has different meaning in python.
10 10
11* Internal utility functions used in the bindings must start with an
12 underscore and must have the shortest name as possible.
13
14Design patterns
15===============
16 * From "The Zen of Python":
17
18 Beautiful is better than ugly.
19 Explicit is better than implicit.
20 Simple is better than complex.
21 Complex is better than complicated.
22 Flat is better than nested.
23 Sparse is better than dense.
24 Readability counts.
25 Special cases aren't special enough to break the rules.
26 Although practicality beats purity.
27 Errors should never pass silently.
28 Unless explicitly silenced.
29 In the face of ambiguity, refuse the temptation to guess.
30 There should be one-- and preferably only one --obvious way to do it.
31 Although that way may not be obvious at first unless you're Dutch.
32 Now is better than never.
33 Although never is often better than *right* now.
34 If the implementation is hard to explain, it's a bad idea.
35 If the implementation is easy to explain, it may be a good idea.
36 Namespaces are one honking great idea -- let's do more of those!
37
11Tips 38Tips
12==== 39====
13 40