Coding Style

Tim Flink tflink at redhat.com
Mon Jun 2 18:04:52 UTC 2014


Since we're likely to be doing some license header changes in the near
future, I'm thinking that it might be a good time to start discussing
code style for our projects.

I'd like to be pretty much pep8 unless there are good reasons to
deviate from that standard. PEP8 is well known and tools to check
against it are widely available.

Outside any header requirements or directive documentation requirements,
are there any changes to PEP8 that folks want to make? If so, please
list the exceptions and why you think they should be adopted.

Tim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/qa-devel/attachments/20140602/6e1d15da/attachment.sig>


More information about the qa-devel mailing list