Clarify that tuple should not be prohibited as an argument to type#2146
Uh oh!
There was an error while loading. Please reload this page.
Conversation
Closespython#2145 This spec change reconciles the typing spec and the conformance testsuite. `tuple` is an object of the `type` class, so it should be accepted as a value of `type`.
srittau added Typing Council decision 
erictraut left a comment
erictraut left a comment There was a problem hiding this comment.
I don't think the new wording should mention tuple at all. It's not a special form. It's simply a class.
The problem here is the phrase special constructs, which is not defined anywhere in the spec and is therefore ambiguous. I think we should change this to special form, which is defined in the glossary.
fangyi-zhou changed the title tuple should be accepted as an argument to typetuple should not be prohibited as an argument to type
encukou commented Jan 8, 2026
Maybe add an extra sentence now? |
erictraut commented Jan 8, 2026
No, this is already covered elsewhere in the spec. We try to avoid redundancies because they create confusion and potential inconsistencies. |
fangyi-zhou commented Jan 8, 2026
@erictraut Do you mean this is covered in the grammar in https://typing.python.org/en/latest/spec/annotations.html#type-and-annotation-expressions? |
erictraut commented Jan 9, 2026
Yes |
5 participants
Closes#2145
This spec change reconciles the typing spec and the conformance testsuite.
tupleis an object of thetypeclass, so it should be accepted as a value oftype.