Skip to content
This repository has been archived by the owner on Dec 7, 2018. It is now read-only.
This repository has been archived by the owner on Dec 7, 2018. It is now read-only.

PEP8 (and maybe later pylint) checks in CodeClimate #34

Open
@spxiwh

Description

Hi @duncanmmacleod. I've recently (for the last month) had codeclimate's PEP8 checker enabled in pycbc, and it has been quite a useful (and not intrusively verbose) checker of PEP8 style (see any recent pycbc pull request ... and associated commits as people actually went and fixed the PEP8 issues!). I'm also lead to believe that pylint will soon be added to the CodeClimate engine as well.

Are you interested in me (or you) adding this also in GWIN? It requires a bit more setup than what I think is there for codeclimate at the moment, but it has worked very well for us so far! ... And I think if I do it, I can just use the same setup I have for pycbc also for gwin (as the permissions setup is over the whole gwastro namespace). (I still miss landscape.io, which was perfect when it worked, but this seems to be doing okay as a replacement).

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions