Why lock on dataclass?

[lev-trullion]

Why lock on a dataclass? Why not just any class?

[oxan]

I've converted this to an discussion, as it's a question and not an actionable issue.

The short answer is because this package uses various features from the dataclasses module (mostly dataclasses.fields and all its metadata processing, but also dataclasses.replace). The longer answer is that there haven't been any requests for regular class support nor do I see it having much added value, and it does require real work in reimplementing all the features from the dataclasses module.

[lev-trullion]

I'd like same library for attrs lib