Skip to content
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

Consider removing locally-enabled #2442

Closed
PCManticore opened this issue Aug 23, 2018 · 0 comments
Closed

Consider removing locally-enabled #2442

PCManticore opened this issue Aug 23, 2018 · 0 comments
Labels
Enhancement ✨ Improvement to a component Good first issue Friendly and approachable by new contributors

Comments

@PCManticore
Copy link
Contributor

Is your feature request related to a problem? Please describe

Feature request. We should consider removing locally-enabled as it is not useful to anyone. locally-disabled probably makes sense if you want to disallow having pragma controls in your source code.

Describe the solution you'd like

Just remove the check.

@PCManticore PCManticore added Enhancement ✨ Improvement to a component Good first issue Friendly and approachable by new contributors labels Aug 23, 2018
The-Compiler added a commit to qutebrowser/qutebrowser that referenced this issue Jun 8, 2022
Looks like 2.14 added bad-option-value:
https://pylint.pycqa.org/en/latest/whatsnew/2/2.14/full.html

locally-enabled is long gone:
pylint-dev/pylint#2442

and so is bad-continuation:
pylint-dev/pylint#3571

no-self-use was moved to an extension in this release:
pylint-dev/pylint#6448
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement ✨ Improvement to a component Good first issue Friendly and approachable by new contributors
Projects
None yet
Development

No branches or pull requests

1 participant