Reduce duplication of code between typing
and typing_extensions
#7075
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following #7037, we now (ab)use the fact that
Protocol
is defined unconditionally intyping.pyi
as a means to avoid redefiningProtocol
intyping_extensions
(we just re-export it fromtyping
). This means that we no longer have to define_ProtocolMeta
intyping_extensions
, since its only purpose is to define theProtocol
class.We can also import the definition of_SpecialForm
fromtyping
, which should help stop them getting out of sync in the future (they are already out of sync now).^Seems like importing
_SpecialForm
breaks pytype, unfortunately.