I don't have a terribly strong opinion about whether or not it is acceptable to use dict.copy, my point was that the desired semantics can be achieved using only dunder methods if desired, and I think at this point getting the semantics right probably matters more than the implementation details. If we all agree on the semantics and we're just trying to decide how to get there, then I suppose I don't have a dog in the fight.
I will note that it doesn't seem to be true that operators never call standard methods. Looks like date.__add__ calls date.toordinal and date.fromordinal (at least in the pure Python implementation), and datetime calls those plus tzinfo.utcoffset. Not sure if the rule Serhiy is citing is only intended to apply to builtins, though. On February 6, 2020 10:25:52 PM UTC, Brandt Bucher <[email protected]> wrote: >Sorry Paul, I sent my reply too soon. > >I see what you're saying, and I'm pretty firmly -1 on reinventing (or >importing) copy.copy. We already have an API for copying a dict >(dict.copy). > >I still fail to see problem with using a method that doesn't start and >end with underscores, other than that we "haven't done it". > >Brandt >_______________________________________________ >Python-Dev mailing list -- [email protected] >To unsubscribe send an email to [email protected] >https://mail.python.org/mailman3/lists/python-dev.python.org/ >Message archived at >https://mail.python.org/archives/list/[email protected]/message/7TQI54BEUN6GERZA3Y2GCXPBD3CHXKM6/ >Code of Conduct: http://python.org/psf/codeofconduct/
_______________________________________________ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/SCDWUIQX4ZLLU72QI4PYEG25W6JVIBFT/ Code of Conduct: http://python.org/psf/codeofconduct/
