Looks interesting, why dataclasses2? Also, how much has changed from the pydantic.dataclasses module?

@samuelcolvin I added dataclasses2 just to showcase the new proposal of implementation.

So I'm pretty happy with the current state of this PR
I added tests for all the linked issues and some more 🤯

The chosen behaviour is

import dataclasses
import pydantic

@pydantic.dataclasses.dataclass
class M1:
    x: int

@pydantic.dataclasses.dataclass
@dataclasses.dataclass
class M2:
    x: int

@dataclasses.dataclass
class M3:
    x: int

VM3 = pydantic.dataclasses.dataclass(M3)

assert M1(x='3').x == 3
assert M2(x='3').x == 3
assert M3(x='3').x == '3'
assert VM3(x='3').x == 3
assert M3(x=3) == VM3(x=3)

The only issue is for the 3rd case, which should be quite rare!
To do that I added a proxy (taken from the great wrapt library). But to work properly we need the proxy to forward inheritance, which is done thanks to __mro_entries__ available since....3.7! 😓

For python 3.6 we hence tolerate a degraded behaviour with a side effect on the stdlib dataclass: it now triggers validation by default. But it can be changed directly in the validator on thanks to a magic kwarg in __init__. The user is naturally notified with a UserWarning!
(It will give even more reasons for people to move to a more recent python version 😆)

@samuelcolvin I wait for your remarks before updating the documentation. It's quite heavy sorry for that!

@PrettyWood another testcase to add to your branch #2594

when using Extra.allow the extra properties don't show up in __str__

from pydantic import Extra
from pydantic.dataclasses import dataclass


class Config:
    extra = Extra.allow


@dataclass(config=Config)
class Foo:
    a: int


foo = Foo(a=1, b=2)

print(foo.b) # 2
print(foo) # Foo(a=1)

when using Extra.allow the extra properties don't show up in __str__

@DetachHead This caveat is documented in 5907f82

is there an issue tracking it? if not i can make one

Can we please merge this and cut a release? :)

@samuelcolvin @ahirner @robons any update on this?

Sorry, been busy with pydantic-core, I'll work on 1.10 soon and this will be included.

@PrettyWood what do you think?

@samuelcolvin taking some days off after a very busy Q2! If you can resolve conflicts, I reckon it's solving a lot of issues with dataclasses. And we'll probably have cleaner logic (and hence code) in v2

This is now just conflicting with #3713, I'm not sure why, I thought I sorted it. Any suggestions? Otherwise I'll dig deeper.

Thank you so much @PrettyWood 🎉, closing 10 issues with one PR must be a record.

Sorry everyone for the delay on this.

ValidatedItem(name='qwe', b=b'1', pydantic_run_validation=False). using pydantic_run_validation doesn't seems to skip validation. I am using pydantic -1.10.2 @samuelcolvin @PrettyWood

I have created a issue for this - #4496