Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing PR #185 on OrkoHunter/PEP8Speaks #443

Conversation

pep8speaks
Copy link
Collaborator

Testing pep8speaks-org/pep8speaks#185


Expected Result -


Hello @pep8speaks! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

Line 2:1: E265 block comment should start with '# '
Line 13:1: E302 expected 2 blank lines, found 1
Line 13:11: E203 whitespace before ':'
Line 14:82: E501 line too long (159 > 81 characters)
Line 16:1: W293 blank line contains whitespace
Line 17:5: E266 too many leading '#' for block comment
Line 18:1: W293 blank line contains whitespace
Line 19:11: E225 missing whitespace around operator
Line 40:1: E305 expected 2 blank lines after class or function definition, found 1


@pep8speaks
Copy link
Collaborator Author

Hello @pep8speaks! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

Line 2:1: E265 block comment should start with '# '
Line 13:1: E302 expected 2 blank lines, found 1
Line 13:11: E203 whitespace before ':'
Line 14:82: E501 line too long (159 > 81 characters)
Line 16:1: W293 blank line contains whitespace
Line 17:5: E266 too many leading '#' for block comment
Line 18:1: W293 blank line contains whitespace
Line 19:11: E225 missing whitespace around operator
Line 40:1: E305 expected 2 blank lines after class or function definition, found 1

@pep8speaks pep8speaks closed this Feb 12, 2021
@pep8speaks pep8speaks deleted the 0e804f0e5fb24c9199843e7ee14be403-test-errors-with-setup.cfg-and-pep8speaks.yml branch February 12, 2021 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants