Message133191
| Author |
ncoghlan |
| Recipients |
Trundle, benjamin.peterson, daniel.urban, docs@python, eric.araujo, ncoghlan, pitrou, rhettinger |
| Date |
2011年04月07日.04:50:18 |
| SpamBayes Score |
1.7196074e-07 |
| Marked as misclassified |
No |
| Message-id |
<1302151819.09.0.724675886969.issue10977@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I thought about a warning, but the problem is that a subclass using the concrete API as part of its *implementation* of the associated slot or method is actually perfectly correct usage.
I'm not sure this is enough to give up on the idea of OrderedDict being a dict subclass implemented in C, though. It seems to me that some defensive internal checks (to pick up state corruption due to this problem) would be a lesser evil than giving up on being a dict subclass. |
|