On Fri, 06 Sep 2013 08:59:02 -0700, Ethan Furman firstname.lastname@example.org wrote:
On 09/06/2013 08:44 AM, R. David Murray wrote:
On Fri, 06 Sep 2013 08:14:09 -0700, Ethan Furman email@example.com wrote:
On 09/06/2013 07:47 AM, Armin Rigo wrote:
Are you suggesting that inspect.getmro(A) would return (A, object, type)? That seems very wrong to me.
Currently, `inspect.getmro(A)` returns `(A, object)`.
Which matches A.__mro__. EOD, I think.
I hope not, because currently this leaves a hole in the introspection of class attributes.
Is __mro__ aimed primarily at instances and not classes? That seems to be how it works. In which case, do we need another __mmro__ (or __cmro__ or ...) to handle the mro of classes themselves?
Or maybe just a new inspect function?
For the short term I can restrict the change to inspect.classify_class_attrs().
Sounds like the best course.