On Oct 18, 2019, at 12:17, Gus Wiedey <[email protected]> wrote: > > I actually have a commit already made, but I realized there is one possible > complication that I may have overlooked: if there are keys in __kwdefaults__ > that don't correspond to any explicitly-named arguments in the signature, > will those get ignored or could they cause problems?
Aren’t __defaults__ and __kwdefaults__ mutable, so this exact same issue can arise today? I think it’s worth testing anyway (and testing both with and without a **kw, and maybe testing what happens with too many __defaults__ too), but unless the result is something like “the constructor segfaults”, it seems like probably it’s fine to keep doing it, and if not it’s probably a separate bug from the one you’re fixing. _______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/XKVQNOG7NY3UIEJVIVCIIF7UMX2YJEG2/ Code of Conduct: http://python.org/psf/codeofconduct/
