-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 options #5740
Remove deprecated options #5740
Conversation
All print a message; most are ignored except where marked: --disallow-any -f/--dirty-stubs --use-python-path (would exit with error message) -s/--silent-imports (would set ignore_missing_imports=True and follow_imports=skip) --almost-silent (would set follow_imports=error) --[no-]fast-parser
(Putting this in a separate commit since it's more controversial -- since it did work, some people might still be using it, even though it's been deprecated since May 2017. See discussion in python#3195.)
Regarding the strict-boolean flag -- maybe one idea might be to move that sort of logic into a separate plugin that's independent from mypy. I've been vaguely thinking about doing this myself, actually -- I can never remember what's supposed to be truthy or falsey from language to language, so most of my personal code is written in a style where this sort of plugin would actually be mildly useful/not very noisy. I'm not sure if our plugin system would support these kinds of extensions yet though. |
I don't think the plugin system could do that unless there was a way to
request being called for every expression.
|
Hm, it seems I did the wrong thing trying to make flake8 happy. Sorry! |
No worries, I'll fix it.
|
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.
Glad to see so many negative lines of code and removed options. I think that it's fine to remove these deprecated options now.
These will now all fail with
unrecognized arguments: <flag>
I've put the removal of
--strict-boolean
in a separate commit since it's more controversial -- some people might still be using it, even though it's been deprecated since May 2017. See discussion in #3195.