examples: fully automated fixing of E30 pep8 errors #3513
Merged
Conversation
This file contains hidden or 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
Member
|
This appears to have broken building the documentation. |
Signed-off-by: Thomas Hisch <t.hisch@gmail.com>
steps to reproduce (autopep8 -i --select E111 */*.py) + remove changes in non-empty lines Signed-off-by: Thomas Hisch <t.hisch@gmail.com>
twmr
force-pushed
the
examples_whitespace_fixes
branch
from
1b43ea7 to
4f0a481
Compare
Contributor
Author
|
@tacaswell fixed, accidentally committed a temporary file |
Member
|
Merging this is 100% changes to blank lines/trailing white space. |
tacaswell
added a commit
that referenced
this pull request
Sep 14, 2014
PEP8 : fix blank-line violations in examples
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
probably these simple newline fixes (pep8 E30x error classes - see https://pep8.readthedocs.org/en/latest/intro.html#error-codes) in all mpl examples are less controversial than my pep8 changes in #3425 and #3488.
For this PR I used my patched versions of pep8 and autopep8 - no manual adjustment was required - yeah :)