-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
move Callable
and other types that don't belong in collections.abc
to another module
#126470
Comments
+ |
+1 |
+1, would you like to submit a PR? |
Duplicate: #69823 |
sure. what module should i put them in? or should i just un-deprecate them for now so a decision can be made in the future regarding where they should go?
that issue is quite old and seems to have been closed without a proper solution, so if we close this issue as a duplicate i think that one should be re-opened |
Moving them would break a ton of code. Please discuss this on discuss.python.org first. |
I agree, this needs a discussion first. For now I will close the issue. |
Feature or enhancement
Proposal:
types like
Callable
andAwaitable
are completely unrelated to "collections", thereforecollections.abc
is clearly the wrong place for them, so the fact thattyping.Callable
andtyping.Awaitable
are deprecated in favor of these aliases is very confusing.imo they should either be moved to a different module, or the versions in
typing
should be un-deprecated until a more suitable location for them is decidedHas this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
The text was updated successfully, but these errors were encountered: