PEP8Speaks itself has dozens of PEP 8 issues about pep8speaks HOT 3 CLOSED

I started looking at PRs here for an example of pep8speaks in use. It seems it might serve multiple purposes to "eat your own dogfood" in this case. Using pep8speaks on this project will provide a demonstrate the features, and also help to clean up the violations in the project.

I hope this is taken as constructive.

from pep8speaks.

Also, at the same time, I can fix a couple related standards-compliance issues, namely:

• A few files are missing terminating EOLs, as is required by a number of standards (and triggering Git warnings, breaking a number of *nix utilities, etc), namely:

  pep8speaks/__init__.py
  requirements/test.txt
  templates/index.html
  tests/__init__.py
  

• A number of files are missing the # -*- coding: utf-8 -*- line required by PEP 263; however, if its not compatible with Python 2 or at least realistically expected to be run on such, then it isn't strictly necessary. The files:

  ./conftest.py
  ./pep8speaks/constants.py
  ./pep8speaks/models.py
  ./pep8speaks/utils.py
  ./pep8speaks/__init__.py
  ./tests/pep8speaks/test_handlers.py
  ./tests/pep8speaks/test_helpers.py
  ./tests/pep8speaks/test_models.py
  ./tests/pep8speaks/test_utils.py
  ./tests/test_app.py
  ./tests/__init__.py
  

from pep8speaks.

Hi @CAM-Gerlach ! Thank you for your suggestions on the PEP 8 issues and note about EOLs. I agree that the code itself had those issues.

As of today, there are no style issues detected by pycodestyle in the project. As a note, I would like to add that there are some configurations of pycodestyle that this project uses. I should probably add it to cfg files for other tools to read them. Related : #95

from pep8speaks.