Drop Python 3.6 in typing_extensions

[AA-Turner]

Python 3.6 is now end of life (python/peps@58b93bd)

This drops support and does various cleanup things (see commits for more detail).

Hopefully this would make e.g. #963 easier (xref #963 (comment))

A

[srittau]

+1 from me, but I know some people are in favor of supporting 3.6 for a while longer. On the other hand, typing-extensions 4 is still available.

[hauntsaninja]

Is PEP 646 the only thing that will be included in the short-term future? If so, +1 from me. If not, might be nice to get those in, although as srittau says, we could always backport (but that's a hassle).

[JelleZijlstra]

The only other thing that is on the horizon right now is dataclass_transform I believe. (There are also pending PEPs for Literal[str] and callable syntax, but those shouldn't affect typing-extensions. We already support Self.) But dataclass_transform will mostly be a stub-only thing, so it doesn't seem too important to support at runtime in typing-extensions.

[srittau]

A minor wish: Could we split the changes to the workflow file (except for dropping 3.6) out into a separate PR for a cleaner history?

[AA-Turner]

Only dropping 3.6 remains in this PR, see #1017

A

[JelleZijlstra]

I'd like to do one more release (4.1.0) with 3.6 support for the PEP 646 objects. After that we can drop 3.6. It should not require a major version change though, it can just be 4.2.0.

[AA-Turner]

Updated the version number to 4.2.0 -- I can merge in master now to resolve conflicts, or wait until PEP 646 support &c has been released in v4.1.0. Which would you prefer?

A

[JelleZijlstra]

Thanks! I'd suggest to defer dealing with the merge conflicts until we're ready, because you'll just get new ones if there are any additional changes.

[srittau]

Converted to draft to signal that we are "waiting for stuff". Please unconvert once 4.1.0 has been released.

[srittau]

Superceded by #1104. Thanks!