Skip to content
Back to Milestones

Code style analysis

Open
Overdue by 8 year(s)
Due by July 1, 2017
Last updated Feb 26, 2017

We want to be able to check for if code is PEP8 compliant.

This emerged after running pylint and getting a wrong result, example:

1: import module_name
2: from module_name import class_name

1 usage: module_name.class_name
2 usage: class_name

If there are global name clashes this should not be converted, pylint cannot do this.

0% complete

List view

    There are no open issues in this milestone

    Add issues to milestones to help organize your work for a particular release or project. Find and add issues with no milestones in this repo.