-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Remove deprecated functions and classes #8409
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #8409 /- ##
=======================================
Coverage 95.68% 95.68%
=======================================
Files 176 175 -1
Lines 18504 18465 -39
=======================================
- Hits 17705 17668 -37
Misses 799 797 -2
|
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.
We need to explain what's the alternative, for example "To make a checker reduce map data simply implement get_map_data and reduce_map_data." etc. etc. (We can copy paste from the deprecation message and adapt).
doc/whatsnew/fragments/8409.breaking
Outdated
A number of old utility functions and classes have been removed. | ||
These are ``MapReduceMixin``, ``is_inside_lambda``, ``check_messages``, | ||
``is_class_subscriptable_pep585_with_postponed_evaluation_enabled``, | ||
``get_python_paht``, ``fix_import_path`` and ``get_global_option``. |
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.
``get_python_paht``, ``fix_import_path`` and ``get_global_option``. | |
``get_python_path``, ``fix_import_path`` and ``get_global_option``. |
I was wondering about that. It feels as if the changelog can become very long. Shouldn't we just refer to the code and let the old |
Yeah it's going to be long but it's the place where people are going to look first when something break, so it needs to explain what to do imo (also if someone is taking care of the deprecation warnings they won't need it). |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
b4e6e9d
to
d7db439
Compare
@Pierre-Sassoulas LGTM! |
But docs fail :( |
This comment has been minimized.
This comment has been minimized.
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 don't think we can use enumeration in the fragments, because it's already inside an enumeration. It's probably fixable but also not worth imo.
π€ Effect of this PR on checked open source code: π€ Effect on django:
Effect on music21:
The following messages are no longer emitted:
Effect on pandas:
The following messages are no longer emitted:
This comment was generated for commit 3b4d040 |
Changelog: https://pylint.pycqa.org/en/latest/whatsnew/3/3.0/index.html#summary-release-highlights remove `__implements__`: That attribute is apparently from a rejected PEP. They say to inherit from BaseChecker, which we are already doing. pylint-dev/pylint#8404 check_messages -> only_required_for_messages: Seems straightforward instructions. I haven't actually tested it. pylint-dev/pylint#8409 remove emptystring extension: Looks like this has been replaced by https://pylint.readthedocs.io/en/stable/user_guide/messages/convention/use-implicit-booleaness-not-comparison-to-string.html Which is disabled by default but we have `enable=ALL`, so I guess that means we indeed have it enabled. And update changelog URLs.
Type of Changes
Description
We're getting there.