-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
False positive bad-continuation error #638
Labels
Comments
Problem persists in pylint 1.6.1. |
I don't think this was actually solved. |
+1 |
1 similar comment
+1 |
Still in 1.7.4. |
The issue is not closed yet, so even if there is a new release, it won't be part of it. |
x539
pushed a commit
to x539/pylint
that referenced
this issue
Mar 17, 2018
x539
pushed a commit
to x539/pylint
that referenced
this issue
Mar 17, 2018
brycepg
pushed a commit
that referenced
this issue
Mar 25, 2018
@PCManticore: this bug was already reported by @pylint-bot in 2014. Can we continue the discussion in #289, please? |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally reported by: Tim Leslie (BitBucket: timl, GitHub: @timl?)
PEP 8 states:
The following code, which is valid according to PEP8,
gives this error:
I'm currently running the latest pylint installed via pip (1.4.4).
The example taken directly from the PEP 8 text does not produce the error:
The text was updated successfully, but these errors were encountered: