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 daniel.urban
Recipients amaury.forgeotdarc, daniel.urban, georg.brandl, pwerneck, rodsenra, terry.reedy
Date 2011-01-28.16:30:52
SpamBayes Score 5.189898e-05
Marked as misclassified No
Message-id <1296232253.32.0.787989656278.issue1294232@psf.upfronthosting.co.za>
In-reply-to
Content
It seems, that this possible problem already came up when __build_class__ got implemented, see issue1681101. The second and third version of the patch at this issue (file7874 and file7875) contains a comment: "XXX Should we do the "winner" calculation here?". But the next version, which contains the C implementation of __build_class__ still uses simply the first base. The "winner calculation" probably refers to the algorithm determining the proper metaclass in lines 1950-1976 of typeobject.c (in type_new).
History
Date User Action Args
2011-01-28 16:30:53daniel.urbansetrecipients: + daniel.urban, georg.brandl, terry.reedy, amaury.forgeotdarc, rodsenra, pwerneck
2011-01-28 16:30:53daniel.urbansetmessageid: <1296232253.32.0.787989656278.issue1294232@psf.upfronthosting.co.za>
2011-01-28 16:30:52daniel.urbanlinkissue1294232 messages
2011-01-28 16:30:52daniel.urbancreate