-
-
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
Deprecate extension-pkg-whitelist #7118
Conversation
Pull Request Test Coverage Report for Build 2605822650
💛 - Coveralls |
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 should actually deprecate this one. If we have the capability to auto-upgrade the configuration we don't need to deprecate, and if we don't then it's forcing work on our user to fix something that is not broken.
I mean, I'm not personally offended by this in anyway but if some users are, why wouldn't we put in a little effort to alleviate that? We already have the functionality to do so, so why not use it? I get that the discussion is a bit political, but it doesn't really hurt those who aren't offended and might help those who are. |
It's not only us doing the effort but every users that will need to upgrade their conf for 3.0. I don't want users to have to upgrade their conf in general... but in particular I don't want them to have to upgrade their configuration for political reasons. And I especially don't want to deal with bigots that had to upgrade their configuration and now have a strong desire to tell us about the etymology of blacklist. Let's not create political breaking change, and let's not trigger anyone. If we do #5462 then we'll be able to clean up configuration. The amount of work to do this issue is tiny in comparison of the work involved for all pylint users to upgrade all their conf and probably comparable to the bigot handling we'd have to do for this anyway. |
Should we close the related issue then? @jacobtylerwalls I noticed the |
Type of Changes
Description
Ref. #5465
Doesn't close as I also need to deprecate the
black_list
options.