-
-
Notifications
You must be signed in to change notification settings - Fork 264
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
aiohttp.ClientSession() crashes pylint #2075
Comments
Please copy the content of the stack trace into the issue description. Maintainers are not likely to download random files from the internet because of the apparent security risks 😄 |
Thank you for opening the issue :) Don't worry, I included the stacktrace in the issue. |
@jacobtylerwalls Are you able to reproduce this? I can't: ❯ cat test.py
import aiohttp
s = aiohttp.ClientSession()
❯ pylint --version
pylint 3.0.0b1
astroid 2.16.0dev0
Python 3.11.0b3 (main, Jun 12 2022, 16:13:11) [Clang 13.0.0 (clang-1300.0.29.30)]
❯ pylint test.py
--------------------------------------------------------------------
Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00) |
No, I can't. But the stack trace looks like something important to fix, somewhere downstream of the namedtuple/enum brain an Uninferable got attached to the |
Yeah, although that might also be a downstream package breaking something. Without an actual reproducer this will just stay open indefinitely.. |
Hello Folks, It turns out this issue is due to using the embeded python installation (due to some restrictive admin policy on the server I'm using) A regular installation of python does not generate this issue. Here is a script I used to reproduce the issue with a fresh installation of python.
Replace the embeded python with regular python and the pylint works fine. Is embeded python expected to work for this? |
Sorry I don't think we support this. I don't have much experience with embedded python installations. @jacobtylerwalls do you? |
No I don't; reproducing in exactly the form the report takes will be difficult. Still, the reason I was tempted to put "good first issue" (which I removed once I realized we didn't have a convenient repro) is that we should identify where an Uninferable is being set on .args. We could probably construct a different reproducer that does that. |
Bug description
When parsing the following file:
Command used
Pylint output
pylint crashed with an ``AstroidError`` and with the following stacktrace
Expected behavior
not to crash
Pylint version
OS / Environment
Windows
Additional dependencies
aiodns==3.0.0
aiohttp==3.8.4
aiosignal==1.3.1
astroid==2.15.1
async-timeout==4.0.2
attrs==22.2.0
autopep8==2.0.2
certifi==2022.12.7
cffi==1.15.1
charset-normalizer==3.1.0
colorama==0.4.6
dill==0.3.6
frozenlist==1.3.3
idna==3.4
isort==5.12.0
lazy-object-proxy==1.9.0
mccabe==0.7.0
multidict==6.0.4
mypy==1.1.1
mypy-extensions==1.0.0
platformdirs==3.2.0
pycares==4.3.0
pycodestyle==2.10.0
pycparser==2.21
pylint==2.17.1
requests==2.28.2
tomlkit==0.11.7
types-requests==2.28.11.17
types-urllib3==1.26.25.10
typing_extensions==4.5.0
urllib3==1.26.15
wrapt==1.15.0
yarl==1.8.2
The text was updated successfully, but these errors were encountered: