-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
pylint crashed with a AstroidError
#8866
Comments
Thanks for this @kornoa! The reproducer can be simplified to: class A:
def say_hello(self) -> __module__:
... |
At first glance, |
I got another NoneType in an Astroid callback, but with this code: from dataclasses import dataclass
from enum import Enum
@dataclass
class Status(Enum):
OFF = 0
I can reproduce it in a minimal venv from this requirements.txt:
From this, I can also reproduce the simplified reproducer above. |
Thanks for checking old issues. That seems to be #9100 which is resolved on |
Bug description
pylint crashed with a
AstroidError
Configuration
Command used
Pylint output
Expected behavior
No exception
Pylint version
OS / Environment
cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
Additional dependencies
cat /home/knoack/.cache/pylint/pylint-crash-2023-07-20-13-04-04.txt
First, please verify that the bug is not already filled:
https://github.com/PyCQA/pylint/issues/
Then create a new crash issue:
https://github.com/PyCQA/pylint/issues/new?assignees=&labels=crash%2Cneeds+triage&template=BUG-REPORT.yml
Issue title:
Crash ```` (if possible, be more specific about what made pylint crash)
Content:
When parsing the following file:
pylint crashed with a
AstroidError
and with the following stacktrace:The text was updated successfully, but these errors were encountered: