coding style

[GoogleCodeExporter]

I suggest we put it somewhere and I suggest we simply take the Enthought one:

https://svn.enthought.com/enthought/browser/sandbox/docs/coding_standard.py

Well, maybe you won't like it, that they use the standard that I am saying
all the time, but you refuse. :))

Original issue reported on code.google.com by ondrej.c...@gmail.com on 1 Aug 2008 at 8:45

[GoogleCodeExporter]

What is there that is not in the PEP? It seems that they force docstrings 
(good),
allow {eggs : 2} which is not allowed in the PEP (also good), and are pretty 
generous
with using spaces in arithmetic operations (I put spaces usually everywhere, 
but do
not care much as long as it is readable -> ok).

We can use plurals in module names and it will stay that way.

spam( ham[ 1 ], { eggs: 2 } ) is bad, which is good

spam( ham[1], {eggs : 2} ) is good for me and will stay good

Agreed that we should put it somewhere.

Original comment by robert.c...@gmail.com on 5 Aug 2008 at 10:16

[GoogleCodeExporter]

Yeah, let's just use PEP. Well, it doesn't matter that much with me. 

Original comment by ondrej.c...@gmail.com on 5 Aug 2008 at 11:07

[GoogleCodeExporter]

We use the PEP by now in new code and more and more in the old code as well.

Original comment by robert.c...@gmail.com on 3 Nov 2011 at 10:08

• Changed state: Fixed

[GoogleCodeExporter]

Migrated to http://github.com/sfepy/sfepy/issues/57

Original comment by robert.c...@gmail.com on 30 Jan 2012 at 10:25

• Changed state: Migrated