* Juan BC <[email protected]> [2016-06-12 19:00:23 +0000]: > as i say before, i am no interested in how is a quality of a project based > on the tolerance of their own community. > > Mi interest is the quality based on a random sample of code from a random > sample of programmers. I use flake because my index of quality is based > also on flake8.
Using flake8 errors as a measurement of quality is flawed to begin
with, in my opinion.
As Ian said, coding style is subjective. If a project has their own
style guide instead of following pep8 (maybe because it was created
before pep8 was widespread, like Twisted I believe, or many parts of
the stdlib), does it have a worse quality? I don't believe so.
Even pep8 says:
Many projects have their own coding style guidelines. In the event
of any conflicts, such project-specific guides take precedence for
that project.
A style guide is about consistency. Consistency with this style
guide is important. Consistency within a project is more
important. Consistency within one module or function is the most
important.
[...]
Some other good reasons to ignore a particular guideline:
[...]
- Because the code in question predates the introduction of the
guideline and there is no other reason to be modifying that
code.
Florian
--
http://www.the-compiler.org | [email protected] (Mail/XMPP)
GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
I love long mails! | http://email.is-not-s.ms/
signature.asc
Description: PGP signature
_______________________________________________ code-quality mailing list [email protected] https://mail.python.org/mailman/listinfo/code-quality
