➜

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 flox
Recipients flox, jcea, pitrou, pjenvey, python-dev
Date 2011-12-18.11:28:34
SpamBayes Score 0.00030176656
Marked as misclassified No
Message-id <1324207774.89.0.705334284611.issue13575@psf.upfronthosting.co.za>
In-reply-to
Content 
> Is mro_internal's second call to type_mro_modified still needed?

I was about to remove it, however I'm not enough confident on this.
I have to understand how "tp_mro" and "tp_bases" interact in Python 3 (and the C extensions).
History
Date User Action Args
2011-12-18 11:29:35floxsetrecipients: + flox, jcea, pitrou, pjenvey, python-dev
2011-12-18 11:29:34floxsetmessageid: <1324207774.89.0.705334284611.issue13575@psf.upfronthosting.co.za>
2011-12-18 11:28:34floxlinkissue13575 messages
2011-12-18 11:28:34floxcreate