Mentions légales du service

Skip to content

[ci] Add pep8-naming checks for flake8

E. Madison Bray requested to merge embray/ci/pep8-naming into master

I did not realize that it does not already check naming by default without a plugin.

This adds some enforcement to use of PEP-8 Naming Conventions for classes, variables, functions, etc.

It is okay to make exceptions to this of course. To quote the opening of PEP-8:

A Foolish Consistency is the Hobgoblin of Little Minds

That is, this is simply a guideline. Try to stick to PEP-8 in general, and when making exceptions know why you want to make this exception (for consistency with existing code, clarity, etc.). You can add exceptions to the setup.cfg file under [flake8]/ignore_names.

Did a few minor variable renamings to make it happy, but we don't always have to go crazy doing this; it's fine to make exceptions sometimes (you can see there are a few exceptions added in setup.cfg).

In the case of some of the property subclasses this is following the trend set by Python of naming most decorators all-lowerclass (even if they happen to be implemented as classes).

Merge request reports