Raise errors on unbound TypeVars with values by sobolevn · Pull Request #15732 · python/mypy (original) (raw)
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 andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation3 Commits4 Checks0 Files changed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})
Completes a TODO item :)
Refs #15724
This comment has been minimized.
…into typevars-with-values
Diff from mypy_primer, showing the effect of this PR on open source code:
mitmproxy (https://github.com/mitmproxy/mitmproxy)
- mitmproxy/tools/console/grideditor/base.py:22: error: A function returning TypeVar should receive at least one argument containing the same TypeVar [type-var]
operator (https://github.com/canonical/operator)
- ops/pebble.py:245: error: A function returning TypeVar should receive at least one argument containing the same TypeVar [type-var]
sobolevn added a commit to sobolevn/operator that referenced this pull request
Hi! While working on python/mypy#15732 our tools detected a misuse of AnyStr TypeVar (which is quite common). The proper way is to use Union here :)
sobolevn added a commit to sobolevn/mitmproxy that referenced this pull request
Hi! While working on python/mypy#15732 our tools detected a misuse of AnyStr TypeVar (which is quite common). The proper way here is to use @overloads :)
mhils pushed a commit to mitmproxy/mitmproxy that referenced this pull request
- Remove incorrect usage of
typing.AnyStr
Hi! While working on python/mypy#15732 our tools detected a misuse of AnyStr TypeVar (which is quite common). The proper way here is to use @overloads :)
- [autofix.ci] apply automated fixes
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
benhoyt pushed a commit to canonical/operator that referenced this pull request
Hi! While working on python/mypy#15732 our tools
detected a misuse of AnyStr TypeVar (which is quite common). The
proper way is to use Union here :)
lasting-yang pushed a commit to lasting-yang/mitmproxy that referenced this pull request
- Remove incorrect usage of
typing.AnyStr
Hi! While working on python/mypy#15732 our tools detected a misuse of AnyStr TypeVar (which is quite common). The proper way here is to use @overloads :)
- [autofix.ci] apply automated fixes
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2 participants
