[cheesecake-dev] Negative scores?

[Grig Gheorghiu]

On 2/3/07, Will Guaraldi <willg at bluesock.org> wrote:
> Regardless, I'm not wildly excited about the pep8 scoring in the first
> place.  The top of pep8 talks about how it's better to have readability
> than a strict conformity of pep8.  On top of that, while pep8 does provide
> a decent style guide and they use it for the stdlib, I don't think that
> it's the _only_ good style guide.  I think it's better for cheesecake to
> test for style consistency within a project rather than strict conformity
> with pep8.
>
> I think that questions like "are there unit tests for this project" are
> important, but questions like "does this project use 4-space indentation"
> are not.  Doing a skim of pep8 module, I think many of the pep8 rules fall
> into the latter category.
>
> I think this particular check hurts projects more than it helps people as
> it's currently implemented.  I think in order to get around the issues I
> have, projects would need to be able to specify the coding style to check
> for consistency on.  Perhaps some specification method like they have for
> checkstyle (http://checkstyle.sourceforge.net/).  Something like that with
> a very lenient default would be better.

Yeah, I think your arguments are valid. So maybe, considering that
pep8 is also hard to score, we can make it an optional check that
Cheesecake can run as a benefit to a package creator, but with no
score attached to it. And by default Cheesecake will not run it. This
way, people who are interested in PEP8-compliance of their code can
still get feedback on where their code stands, and that feedback will
consist in whatever pep8.py reports.

Grig