-
Notifications
You must be signed in to change notification settings - Fork 179
Use PyLint 3.0+ #672
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
Use PyLint 3.0+ #672
Conversation
Pierre-Sassoulas
left a comment
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.
I did not try to just vendor the missing deprecated function in prospector yet, did you think about it ?
|
When I saw the cleaning pull request, the missing function uses a lot of deprecated, then removed objects, then I didn't think that's easy to do! |
f183dc8 to
bed9383
Compare
86ff5ac to
5097b66
Compare
17de0a4 to
971dc91
Compare
971dc91 to
683f0b3
Compare
|
|
||
| found_files = _get_test_files("testpath", "testpath/test_useless_suppression.py") | ||
| pylint_tool.configure(config, found_files) | ||
| # useless-suppression is now disable by default in pylint |
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.
683f0b3 to
359e573
Compare
|
@Pierre-Sassoulas @carlio Do you think that's ready to be merged? As I currently understand, if we want a better (more direct) implementation, we should do some modifications directly in PyLint! |
Pierre-Sassoulas
left a comment
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.
Looks great !
carlio
left a comment
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.
Looks good to me
|
Thank you :-) Do we want something other in version 1.12 or do we do the release? |
|
I think it's best to release it now as people are waiting for a Python 3.12 compatible version; any other bugfixes or cleanups can go into a patch version. I am pretty sure the PyPI token secrets in the repo are still correct so the GitHub action can still be used to make the release, if you want to. |
|
You need to push a tag then create a github release from the tag to release on pypi @sbrunner (I could do it if you want, but it's a good thing if you already did it once imo) |
|
https://github.com/prospector-dev/prospector/blob/master/pyproject.toml#L3 <-- need to update that :) |
|
It's on release creation => Done :-) |
Based on #671, fix some errors