Fix flake8 warnings W605, W504 #2256
Merged
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
|
Can you fill in the PR description please? The PR name and the codes are too cryptic: What is this PR for, why (motivation), what was the main approach for its fix(es)? |
horpto
changed the title
|
Nice, thank you @horpto 👍 |
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.
Since recent release of flake8 (v3.6.0, 24.10.18) all PR-s have not been building due to new warnings W605 W504 (pycodestyle - dependence of flake8, version 2.4.0).
Now, by edited pep 8 you should break the line before binary operator, not after. And avoid slash with followed non-special character like 'i', '*' or others in non-raw string.
Also, here we pin
flake8-rst == 0.4.3until bug with E402 ("glue" rst) will be fixed.