-
-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Deprecate typing.Text
#92332
Comments
I agree on deprecating To reduce cognitive load on readers of the |
We agree. |
Please forgive my ignorance: I didn't even know |
It's pretty easy to miss :). To be clear, by "a long time" I mean something like "wait a decade and then maybe start thinking about removing it". We shouldn't set a concrete removal timeline yet. |
It's definitely not a big maintenance burden or anything! |
Co-authored-by: Shantanu <12621235+hauntsaninja@users.noreply.github.com>
Feature or enhancement
The
typing
module has a huge API, and new features continue to be added in each version of Python. Deprecations should be done carefully and slowly, to minimise disruption for users, but we should nonetheless aim to shrink the API where features are no longer needed, so as to make the sheer size of the module less overwhelming for newcomers to Python typing.Python 2.7 is now end-of-life, so
typing.Text
has no use anymore (its sole purpose was to provide backwards compatibility with Python 2). I propose that we should now deprecatetyping.Text
, with a view to eventually removing it.The text was updated successfully, but these errors were encountered: