Skip to content

Clarify that tuple should not be prohibited as an argument to type #2146

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.

Sign up for GitHub

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

Open
fangyi-zhou wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Clarify that tuple should not be prohibited as an argument to type #2146

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
86f7688
Clarify that `tuple` should be accepted as an argument to `type`
fangyi-zhou Jan 6, 2026
bd28442
Fix wordings for special form
fangyi-zhou Jan 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/spec/special-types.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -188,8 +188,9 @@ concrete class object, e.g. in the above example::
``type[T]`` where ``T`` is a type variable is allowed when annotating the
first argument of a class method (see the relevant section).

Any other special constructs like ``tuple`` or ``Callable`` are not allowed
as an argument to ``type``.
Any other special constructs like ``Callable`` are not allowed
as an argument to ``type``,
but ``tuple`` is allowed as an argument to ``type``.

There are some concerns with this feature: for example when
``new_user()`` calls ``user_class()`` this implies that all subclasses
Expand Down