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
CI: Pylint 3.x #3110
base: master
Are you sure you want to change the base?
CI: Pylint 3.x #3110
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible to just extract the changes to the Python version support and skip the rest, please? I'm not seeing the(pylint comments, inotify import changes, or signal import renaming as relevant to the PR description.
|
@pajod I'm happy to review the linting-related changes in this PR or separate, your choice. Let's just get the pypy version fixed up and I think we're good to go. |
Is there a timeline when this will be merged? |
just to ease static code analysis, no functional change intended
Just to ease static code analysis, no functional change intended. Could have aliases just the other two lines, but chosing the leaked stdlib name ensures nobody should have depended on API stability.
Pylint 3.0 is the first version to officially support Python 12
Debian buster EoL since 2022-09-10
Most of this PR was already merged in #3131
What remains:
What is not included but should probably follow after deciding what to do about the
signal
renaming hack submitted here: