[issue39078] __function.__defaults__ breaks for __init__ of dataclasses with default factory

Eric V. Smith added the comment: I don't think there's any action to be done here, so I'm going to close this. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue39078] __function.__defaults__ breaks for __init__ of dataclasses with default factory

Change by Petr Viktorin : -- components: +Library (Lib) -C API ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue39078] __function.__defaults__ breaks for __init__ of dataclasses with default factory

Eric V. Smith added the comment: I guess I could make the default value something like _CALLABLE(dict), but I'm not sure that would do you any good. But at least you could tell from the repr what it is. -- ___ Python tracker

[issue39078] __function.__defaults__ breaks for __init__ of dataclasses with default factory

Eric V. Smith added the comment: The problem is that __init__ has to have a sentinel to know whether or not to call the default value. If the default were just "dict", should it call it, or is the passed in value really dict, in which case it doesn't get called? dataclass() class Test:

[issue39078] __function.__defaults__ breaks for __init__ of dataclasses with default factory

Change by Eric V. Smith : -- assignee: -> eric.smith nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue39078] __function.__defaults__ breaks for __init__ of dataclasses with default factory

New submission from Veith Röthlingshöfer : When creating a dataclass with a default that is a field with a default factory, the factory is not correctly resolved in cls.__init__.__defaults__. It evaluates to the __repr__ of dataclasses._HAS_DEFAULT_FACTORY_CLASS, which is "". The expected