-
-
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
@typing.no_type_check_decorator is nonfunctional #6583
Comments
There's now a typeshed stub: python/typeshed#3460 (comment) |
Can someone advise on how to track within mypy that a function acts as no_type_check? The current no_type_check appears to be handled via the hardcoded path in a few places. |
Although in general we don't like adding new flags to "important" nodes, it looks like in this case this is the only way (because the other way I see is keeping a global state, which is even worse). You can add a flag to |
…typeshed` (#6583) The original PR doesn't apply cleanly so I only included the changes to builtins to avoid having to manually deal with all the conflicts.
* Typeshed cherry-pick: Relax signature of logging.config.loadConfig (#6577) * Typeshed cherry-pick: Use AbstractSet instead of set in random and inspect (#6574) * Partial typeshed cherry-pick: Add `SupportsRichComparison` type to `_typeshed` (#6583) The original PR doesn't apply cleanly so I only included the changes to builtins to avoid having to manually deal with all the conflicts.
* Typeshed cherry-pick: Relax signature of logging.config.loadConfig (python#6577) * Typeshed cherry-pick: Use AbstractSet instead of set in random and inspect (python#6574) * Partial typeshed cherry-pick: Add `SupportsRichComparison` type to `_typeshed` (python#6583) The original PR doesn't apply cleanly so I only included the changes to builtins to avoid having to manually deal with all the conflicts.
|
I think this firstly needs a typeshed stub, but I think it won't work without special case support in mypy as well.
Related: python/typeshed#2884
The text was updated successfully, but these errors were encountered: