-
-
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
+ pylint-pytest
: pylint crashed with a AstroidError
and with the following stacktrace
#8298
Comments
It seems it's a problem inside pylint-pytest, but right now it's unclear who's maintaining it so let's keep this issue opened until it's clearer. |
Should I like the "maybe-pylint-bug" template - but I think on that case |
There's three libs at work here:
It seems this bug is happening outside of pylint, if you want something to change in pytest you're going to need to open an issue in pytest, if you want something to change in pylint-pytest there's no clear maintainer ship right now, but we plan on maintaining it one way or the other in the midterm see PyCQA/meta#56. |
Sorry, sorry. I meant |
Ha, right. No it's voluntary to not catch the error, we need the stacktrace and a clear fail when something goes wrong (so we get an issue opened and the users have information available). |
I was thinking that, "if you did all that", but then just unloaded the plugin and continue, it would give I'm planning to touch |
Should this be closed already? I think |
You are absolutely right @webknjaz Thank you for the issue-archaeology 🙃 Fixed by pylint-dev/pylint-pytest#12 |
Bug description
Using to "facilitate"
pylint
+pytest
, I receive:Configuration
No response
Command used
bash -c 'test -d .venv && . .venv/bin/activate ; pylint-ignore "$@"' -
... and then files of the repo.
(i.e., called via
pre-commit
)(PS: add the following information on the
~/.cache/pylint/pylint-crash-2023-02-15-14-17-14.txt
file 🙏)Pylint output
Expected behavior
Not-a-stack-trace
Pylint version
OS / Environment
Ubuntu 20.04
Additional dependencies
No response
The text was updated successfully, but these errors were encountered: