E403: add report for module-level dunder names that are misplaced. #1237
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Following post-Y2016 PEP8 style, dunder names declared at the module level should be placed one linespace after any __future__ imports, and one linespace before any other imports.
|
I don't think this should be added. this is a bad suggestion from pep8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the PEP8 Style Guide, dunder names at the module level should be placed before any
importstatements, with the exception of any__future__module imports.There should be a single line of spacing before any module-level dunder names, and a single line of spacing after them; they may be grouped.
Related: