-
-
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
Spurious no-name-in-module
with future.builtins.disabled
on Python 3 with pylint 1.7.0+
#1606
Comments
Note this is new to 1.7.0+:
This does not happen with 1.6.5:
|
no-name-in-module
with future.builtins.disabled
on Python3no-name-in-module
with future.builtins.disabled
on Python3 with 1.7.0+
no-name-in-module
with future.builtins.disabled
on Python3 with 1.7.0+no-name-in-module
with future.builtins.disabled
on Python 3 with pylint 1.7.0+
Note, this also appears to happen with Python 3.5 (not just 3.6):
So this is probably not related to #1072. (See also this comment.) |
I presume we'll need an astroid brain plugin to understand what |
Link to astroid brain plugin docs? |
We don't have great docs for it, it's best to just poke the code in the |
Closing as it's lib specific and with python 2 being dead and buried it's unlikely that this will ever attract the necessary attention to get fixed. |
Test file:
Python 2 works as expected:
Python 3 gets confused:
Possibly related to #1536?
The text was updated successfully, but these errors were encountered: