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 belopolsky
Recipients Alexander.Belopolsky, Robin.Schreiber, amaury.forgeotdarc, belopolsky, loewis
Date 2012-09-06.20:50:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1346964603.67.0.430361240082.issue15870@psf.upfronthosting.co.za>
In-reply-to
Content
> see how type_new also computes the metaclass from the base classes.

As you can see from my first message, I originally considered PyType_FromSpecEx(PyObject *meta, PyType_Spec *spec) without bases.  (In fact I was unaware of the recent addition of PyType_FromSpecWithBases.)  Maybe the original signature makes more sense than the one in the patch.  Explicitly setting a metaclass is most useful for the most basic type. On the other hand, a fully general function may eventually replace both PyType_FromSpec and PyType_FromSpecWithBases for most uses.
History
Date User Action Args
2012-09-06 20:50:03belopolskysetrecipients: + belopolsky, loewis, amaury.forgeotdarc, Alexander.Belopolsky, Robin.Schreiber
2012-09-06 20:50:03belopolskysetmessageid: <1346964603.67.0.430361240082.issue15870@psf.upfronthosting.co.za>
2012-09-06 20:50:03belopolskylinkissue15870 messages
2012-09-06 20:50:02belopolskycreate