This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients Matthias Braun, gvanrossum, petr.viktorin, scoder
Date 2020-06-21.22:00:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1592776847.06.0.322066536988.issue39960@roundup.psfhosted.org>
In-reply-to
Content
That sounds like the right thing to do. You should be able to recognize pure Python __setattr__ implementations by the presence of slot_tp_setattro in the tp_setattro slot. (Likewise for __delattr__.)

It's been really long since I looked at this -- do we still only support single inheritance at the C level? Because otherwise there would be another backdoor.

There's also tp_setattr (no 'o') but I think that's basically unused, and we ignored that in 2003 so we should be able to ignore it now. :-)
History
Date User Action Args
2020-06-21 22:00:47gvanrossumsetrecipients: + gvanrossum, scoder, petr.viktorin, Matthias Braun
2020-06-21 22:00:47gvanrossumsetmessageid: <1592776847.06.0.322066536988.issue39960@roundup.psfhosted.org>
2020-06-21 22:00:47gvanrossumlinkissue39960 messages
2020-06-21 22:00:46gvanrossumcreate