Add support for parametrizing Decoders at runtime #415
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously `Decoder` types could be parametrized in annotations, but only if `__future__.annotations` was imported (they only worked for static analysis tools like mypy/pyright). We now support parametrizing `Decoder` types in python code without `__future__.annotations` for Python 3.9+.
jcrist
force-pushed
the
support-runtime-type-parameter-decoders
branch
from
0fb651c
to
e5aee66
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously
Decodertypes could be parametrized in annotations, but only if__future__.annotationswas imported (they only worked for static analysis tools like mypy/pyright). We now support parametrizingDecodertypes in python code without__future__.annotationsfor Python 3.9+.Fixes #414