Message117885
| Author |
benjamin.peterson |
| Recipients |
Trundle, Yaroslav.Halchenko, benjamin.peterson, daniel.urban |
| Date |
2010年10月02日.16:56:23 |
| SpamBayes Score |
1.7707904e-08 |
| Marked as misclassified |
No |
| Message-id |
<AANLkTi=EbkDEE6gDk7MK1L6v3YW74Jcj4zOQk0KMm_4P@mail.gmail.com> |
| In-reply-to |
<1285994724.21.0.1084942895.issue10006@psf.upfronthosting.co.za> |
| Content |
2010年10月1日 Yaroslav Halchenko <report@bugs.python.org>:
>
> Yaroslav Halchenko <yarikoptic@gmail.com> added the comment:
>
> yikes... surprising resolution -- I expected that fix would either makes __abstractmethods__ accessible in derived "type"s or becomes absent from output of dir() -- but none of those has happened. Now we ended up with a consistent non-Pythonic fate of __abstractmethods__ listed in output of dir() but not accessible. is that a feature?
type has no __abstractmethods__, so it should raise an AttributeError.
Note descriptors are allowed to raise AttributeError even if they're
in dir(). |
|