Yet another metric
So I was just introduced to pyroma (https://pypi.python.org/pypi/pyroma, https://bitbucket.org/regebro/pyroma) which would probably work nicely as a plugin to flake8 or just as a good metric in general. It doesn't exactly measure the quality of the code itself, BUT it does measure the quality of a package which I'm sure would be useful to some (if not many) of our users. I had never thought of analyzing a package for quality beyond it's source (in all candor), so I'm fairly excited about this tool.
On 4/4/13 3:14 PM, Ian Cordasco wrote:
So I was just introduced to pyroma (https://pypi.python.org/pypi/pyroma, https://bitbucket.org/regebro/pyroma) which would probably work nicely as a plugin to flake8 or just as a good metric in general.
It doesn't exactly measure the quality of the code itself, BUT it does measure the quality of a package which I'm sure would be useful to some (if not many) of our users.
I had never thought of analyzing a package for quality beyond it's source (in all candor), so I'm fairly excited about this tool. Interesting
Except: ...If you are checking on a PyPI package, and not a local directory or local package, pyroma will check the number of owners the package has on PyPI. It should be three or more, to minimize the "Bus factor", the risk of the index owners suddenly going off-line for whatever reason... In reality, most companies/org use a single account on PyPI so you can't tell how many developers are behind - so this check seems unpractical. Note that I added a similar thing in python's distutils: the check command. That reminds me of the CheeseCake btw : http://pycheesecake.org/
_______________________________________________ code-quality mailing list code-quality@python.org http://mail.python.org/mailman/listinfo/code-quality
-- Tarek Ziadé · http://ziade.org · @tarek_ziade
On Thu, Apr 4, 2013 at 9:22 AM, Tarek Ziadé <tarek@ziade.org> wrote:
On 4/4/13 3:14 PM, Ian Cordasco wrote:
So I was just introduced to pyroma (https://pypi.python.org/pypi/pyroma, https://bitbucket.org/regebro/pyroma) which would probably work nicely as a plugin to flake8 or just as a good metric in general.
It doesn't exactly measure the quality of the code itself, BUT it does measure the quality of a package which I'm sure would be useful to some (if not many) of our users.
I had never thought of analyzing a package for quality beyond it's source (in all candor), so I'm fairly excited about this tool.
Interesting
Except:
...If you are checking on a PyPI package, and not a local directory or local package, pyroma will check the number of owners the package has on PyPI. It should be three or more, to minimize the "Bus factor", the risk of the index owners suddenly going off-line for whatever reason...
In reality, most companies/org use a single account on PyPI so you can't tell how many developers are behind - so this check seems unpractical.
Note that I added a similar thing in python's distutils: the check command.
That reminds me of the CheeseCake btw : http://pycheesecake.org/
Well if it were a plugin to Flake8 it would only be checking the local directory since Flake8 at no point (as you well know) downloads packages for checks. The I hadn't noticed the check command in distutils (I've never dug that far into it) and I'm looking at CheeseCake now as well. Thanks!
participants (2)
-
Ian Cordasco -
Tarek Ziadé