<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 17 Sep 2017, at 19:17, <a href="mailto:alexandre.galode@gmail.com" class="">alexandre.galode@gmail.com</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi,<div class=""><br class=""></div><div class="">thanks for your answer, and your questions. Very good draw. I printed it in my office ^^</div><div class=""><br class=""></div><div class="">First i'd like to precise that, as in title, aim is not to gurantee quality but minimal quality. I think it's really two different things.</div><div class=""><br class=""></div><div class="">About metrics, my ideas was about following (for the moment):</div><div class=""><ul class=""><li class="">Basical Python Rules respect: PEP8 & PEP20 respect<br class=""></li><li class="">Docstring/documentation respect: PEP257 respect<br class=""></li><li class="">Code readability: percentage of commentary line and percentage of blank line<br class=""></li><li class="">Code maintainability / complexity: the facility to re-read code if old code, or to understand code for an external developer. If not comprehensive, for example, i use McCabe in my work</li><li class="">Code coverage: by unit tests<br class=""></li></ul><div class="">From your question on objective metrics, i don't think that reliable metrics exists. We can only verify that minimal quality can be reached. As you say, it's a subjective apprehension, but in my mind, this "PEP" could be a guideline to improve development for some developers.</div></div></div></div></blockquote><div><br class=""></div><div class="">Quality is something that an organisation and its people need to achieve by building appropriate processes and improvement methods into their work flow.</div><div class=""><br class=""></div><div class="">Trying to be prescriptive will run into trouble for the wider world I suspect.</div><div class=""><br class=""></div><div class="">Many of the maintainability metrics may help a team.</div><div class=""><br class=""></div><div class="">However peer review and discussion within teams is a powerful process to achieve good code, which is process.</div><div class=""><br class=""></div><div class="">I do not see quality as a quantity that can be easily measured.</div><div class="">How can we set a minimum for the hard to measure?</div><div class=""><br class=""></div><div class="">Barry</div><div class=""><br class=""></div><div class="">p.s. Why does this thread have a reply address of <a href="mailto:python-ideas@googlegroups.com" class="">python-ideas@googlegroups.com</a>?</div><div class=""><br class=""></div><blockquote type="cite" class=""><div class="">_______________________________________________<br class="">Python-ideas mailing list<br class=""><a href="mailto:Python-ideas@python.org" class="">Python-ideas@python.org</a><br class="">https://mail.python.org/mailman/listinfo/python-ideas<br class="">Code of Conduct: http://python.org/psf/codeofconduct/<br class=""></div></blockquote></div><br class=""></body></html>