New changeset 7a793a3 by Matthew Rahtz in branch 'main':
bpo-43224: Implement PEP-646 changes to typing.py (GH-31021)
7a793a3

New changeset 5b1b9ea by Serhiy Storchaka in branch 'main':
bpo-43224: Implement substitution of unpacked TypeVarTuple (GH-31800)
5b1b9ea

New changeset af2277e by Matthew Rahtz in branch 'main':
bpo-43224: Implement PEP-646 changes to genericaliasobject.c (GH-31019)
af2277e

New changeset 3a2b895 by Jelle Zijlstra in branch 'main':
bpo-43224: Add TypeVarTuple.__name__ (GH-31954)
3a2b895

Since things are piling up, here's a quick record of what I think the remaining tasks are: (in approximate order of priority)

1. Finish writing docs (is updating library/typing.html sufficient? bpo-47097: Add documentation for TypeVarTuple #32103)
2. Implement support for pickling of unpacked native tuples
3. Implement support and add tests for copy() of TypeVarTuple and unpacked tuple
4. Resolve the issue of how we implement type substitution (https://bugs.python.org/issue47006)

1. Finish writing docs (is updating library/typing.html sufficient? bpo-47097: Add documentation for TypeVarTuple #32103)

We also need to add to the What's New for 3.11. I volunteered to do that for all the typing PEPs.

2. Implement support for pickling of unpacked native tuples

Linking your #76300

3. Implement support and add tests for copy() of TypeVarTuple and unpacked tuple

I believe this uses the same mechanism as pickling, so shouldn't need more work.

New changeset e8e737b by Matthew Rahtz in branch 'main':
bpo-43224: Implement PEP-646 grammar changes (GH-31018)
e8e737b

1. Finish writing docs

Done once #32103 is merged.

2. Implement support for pickling of unpacked native tuples

Done once #32159 is merged.

4. Resolve the issue of how we implement type substitution (https://bugs.python.org/issue47006)

Will re-visit this now.

New changeset 772d808 by Matthew Rahtz in branch 'main':
bpo-43224: typing: Add tests for pickling and copying of unpacked native tuple (GH-32159)
772d808

@mrahtz @JelleZijlstra @serhiy-storchaka Is it okay if I unsubscribe from these conversations and let you all come up with a compromise? I feel that while we ought to have a policy formulated and mostly implemented by beta 1 (May 6), tweaks of both the policy and the implementation during the beta period until RC 1 (Aug/Sept?) should be allowable.

@gvanrossum Fine with me. Godspeed with the rest of your work for this release :)

Keeping track of things yet to do:

• Decide on/implement type substitution behaviour (PEP 646: Decide on substitution behavior #91162)
• Add tests for using * with things in typing.py (e.g. *Tuple[int]) now that the grammar PR has been merged
• Implement support for/add tests for typing.get_args and typing.get_origin on unpacked types
• Add some way of figure out whether a native tuple has been starred (gh-87390: Add __unpacked__ attribute to types.GenericAlias #92059)
• Finish making the runtime produce the results that the substitution tests https://github.com/python/cpython/blob/main/Lib/test/test_typing.py#L581 say it should
• Add substitution test for tuple[*Ts, T][str, *tuple[int, ...]]
• Fix TODOs in test_genericalias.py

Decided against doing:

• Disallow Unpack[Tuple] - I think it's simpler if we keep this valid, in accordance with the the general philosophy of "Keep the runtime lenient when it comes to typing"

How much of the checklist above is still relevant?

Thanks for the reminder! From a quick look, some of the items in the checklist are definitely still relevant. I'll try and find some time for this soon.