You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it is public API in typing.pyi with no indication of being deprecated, would there be any issues in re-exporting this symbol? I understand that it's still not available as a runtime object in typing_extensions.py, if that affects anything.
The text was updated successfully, but these errors were encountered:
I get the impression from the Python docs that typing.type_check_only will remain a non-runtime object, with no plans to put an existent symbol in typing.py. However, since the symbol is wholly defined in typing.pyi, I assumed that the motivation for re-exporting the other symbols from typing would equally apply to type_check_only, allowing one to use typing_extensions in lieu of typing in all situations.
Not a big issue though, since there's plenty of workarounds. Thanks for the response.
@typing.type_check_only
was not explicitly-reexported fromtyping_extensions
as part of the typing-extensions 4.7.* update:typeshed/stdlib/typing_extensions.pyi
Line 70 in 860e34e
As it is public API in
typing.pyi
with no indication of being deprecated, would there be any issues in re-exporting this symbol? I understand that it's still not available as a runtime object intyping_extensions.py
, if that affects anything.The text was updated successfully, but these errors were encountered: