[code-quality] Average number style errors on Python

Ian Cordasco graffatcolmingov at gmail.com
Sun Jun 12 16:18:39 EDT 2016


On Sun, Jun 12, 2016 at 2:00 PM, Juan BC <jbc.develop at gmail.com> wrote:
> as i say before, i am no interested in how is a quality of a project based
> on the tolerance of their own community.

You didn't say that actually.

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

I think you need to watch https://www.youtube.com/watch?v=wf-BqAjZb8M

Following the letter of the document isn't following the spirit and
the quality of a code base can be measured on far more than one axis.
Quality of a code base should also be determined by whether it uses
obvious security problems (as can be caught via bandit) and other
logical errors (as can be caught by pylint). Quality can be further
measured by the tests a project has.

I urge you to reconsider how you're measuring "quality". Instead of
calling it quality, please consider calling it "style conformance".
They are very different things.


More information about the code-quality mailing list