Hello from the PyCharm team! While reading your suggestion, I figured out that there is one technical difficulty for PyCharm. To have a quick code insight (inspections, completion and so on) PyCharm has to build reduced syntax trees. Access to them is faster because some information is omitted (e.g. assigned values, function bodies) and they don't require any parsing as original sources do. This is done during the well-known indexing stage that processes every file independently with no ability to run resolve to other files. With the current proposal, it would be difficult to process dataclasses correctly in one case, I'll comment several examples to shed some light on PyCharm internals: ``` # everything is fine here, # `id` and `name` are saved as a class level attributes; # after indexing is finished, PyCharm is able to figure out that `create_model` describes a dataclass # because resolve becomes available; # same for the example with ModelBase @create_model class CustomerModel: id: int name: str ``` Next sample: ``` # since resolve is not available during indexing, # there is no way to determine if `CustomerModel` is a dataclass # and hence no way to protect `ModelField(default=0)` from being skipped (I've mentioned above that assigned values are omitted) @create_model(init=False) class CustomerModel: id: int = ModelField(default=0) name: str ``` Possible solution for PyCharm would be to save assigned values for all class level attributes (and make indexes more heavy) or to have some predefined names/heuristics to filter out class attributes that can not describe dataclass field. I'd not say it is a major issue, please keep it in mind, I'll be glad to discuss. -- Semyon Proshev, PyCharm --