[1.0 backport] minimal implementation of dataclass_transform (#14523) #14532
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.
This is a very simple first step to implementing PEP 0681, which will allow MyPy to recognize user-defined types that behave similarly to dataclasses.
This initial implementation is very limited: we only support decorator-style use of
typing.dataclass_transform
and do not support passing additional options to the transform (such asfreeze
orinit
).Within MyPy, we add a new
is_dataclass_transform
field toFuncBase
which is populated during semantic analysis. When we check for plugin hooks later, we add new special cases to use the existing dataclasses plugin if a class decorator is marked withis_dataclass_transform
. Ideally we would use a proper plugin API; the hacky special case here can be replaced in subsequent iterations.Co-authored-by: Wesley Wright wesleyw@dropbox.com