-
Notifications
You must be signed in to change notification settings - Fork 3
Support pylint v3 #12
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
Comments
What the status of this issue ? I would like to help if I can |
It is mostly waiting on me to claim back my OSS time and do some basic sanity checks 😅 I apologize that my (announced?) timeline of "having this finished" would be ~Nov-15th, and I am "breaking that promise". |
ok, there is no plan to fix it before v2 ? |
According to Pierre's tries, no: #23 (comment) OTOH, the https://github.com./pylint-dev/pylint-pytest/milestone/1 (all v1.1.x versions) is closed ~1.5w ago, and the https://github.com./pylint-dev/pylint-pytest/milestone/2 is next (i.e., all repo modernizations, which includes upgrading Pythons, dropping If there is a "suitable bugfix" to be done for v1s, we can streamline it now (but it "feels like" pylint-dev/pylint#8298 is not fixable in v1) |
I started something in #27. Unless there is some breaking change I'm not aware of, It seems like we can work with both major 2 and 3 of pylint |
From the issue upstream: pylint-dev/pylint#9144
The text was updated successfully, but these errors were encountered: