-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
te 4.7.0 breaks Mypy daemon on Python 3.7 (TypeError: metaclass conflict
)
#265
Comments
This was fixed in mypy recently (python/mypy#15543) but not released. Given that 3.7 has reached its end of life, we're not planning to fix this in typing-extensions. |
Thanks for the fast response. Could you tell me why |
…g()` (#64) * Remove `Property.config()`, add `Property.required()` and `Property.help` * kraken-std/: improvement: Adjust task property definitions to replace `Property.config()` with `Property.default()` and `Property.default_factory()` * Updated PR references in 1 changelogs. skip-checks: true * try Mypy 1.4.0 * Try Mypy <1.4.0 * use older typing-extensions * fix pyperoject.toml * Set upper constraint for typing-extensions due to python/typing_extensions#265 --------- Co-authored-by: GitHub Action <github-action@users.noreply.github.com>
typing-extensions 4.7 generally works fine with Python 3.7. It's broken only when using dmypy (not mypy itself, which apparently doesn't use any TypedDict), or potentially with other mypyc-compiled applications that use TypedDict. A relatively obscure case in a single third-party tool on a version that has reached end of life isn't enough to justify yanking the release. |
Using
typing-extensions 4.7.0
on Python 3.7 breaks the Mypy daemon:Pinning
typing-extensions 4.6.3
fixes this error. It seems like a break in backwards compatibility in typing-extensions.The text was updated successfully, but these errors were encountered: