Python coding style? (Flake8/PEP8...)

Stephen Gallagher sgallagh at redhat.com
Wed May 7 18:14:40 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/07/2014 09:18 AM, Alois Mahdal wrote:
> Hi,
> 
> what is "official" stance on PEP8 or Pyflake in Python parts of
> OpenLMI?  Or other means of static analysis?
> 
> Most code I've seen does not conform to PEP8 and/or does not pass
> Pyflake test.
> 
> **I'm not trying to say it should**, but ... in case there are no
> objections (or even if it's desired), I'd be happy to go and clean
> up at least lmi.test.* and other test modules I come along
> (common.py, methods.py, ...).
> 
> My motivation:  I use both tests to almost full extent on all my
> Python code (it helps me a *lot* to catch typos and design errors).
> Now when adding my code to existing modules, I get overwhelmed by
> warnings.  Easiest way I can imagine is to to clean up the rest.
> (The next easiest way would be  to set exception on particular
> rules but that only makes sense if it's a project-wide consent.)
> 
> Any comments?



Our coding conventions are listed at
https://fedorahosted.org/openlmi/wiki/CodingConventions#Python

This is pretty loose, and an argument could certainly be made to
standardize on PEP8. I'd like to hear what the main developers think
on the subject.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlNqeBAACgkQeiVVYja6o6N9eQCgiRsLRSTOWxfA4QkGKArcAKlK
EBEAoInzsWuBzGJL0vBNMkBNac4qYPTh
=HmIT
-----END PGP SIGNATURE-----


More information about the openlmi-devel mailing list