sfepy/sfepy — Issue #57: coding style
Author: rc
Created: 2012-01-30 10:25:03+00:00
State: open

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. :))

Migrated from http://code.google.com/p/sfepy/issues/detail?id=53

earlier comments

robert.cimrman said, at 2008-08-05T10:16:25.000Z:

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.

ondrej.certik said, at 2008-08-05T11:07:41.000Z:

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

robert.cimrman said, at 2011-11-03T10:08:43.000Z:

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