➜

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 LambertDW, amaury.forgeotdarc, barronh, belopolsky, grubert
Date 2010-07-20.05:08:38
SpamBayes Score 0.04341554
Marked as misclassified No
Message-id <1279602522.51.0.80758042755.issue5476@psf.upfronthosting.co.za>
In-reply-to
Content 
> Does Numpy correctly call PyType_Ready()?

As far as I can tell, it does:


#define DUAL_INHERIT(child, parent1, parent2)                           \
    Py##child##ArrType_Type.tp_base = &Py##parent2##ArrType_Type;       \
    Py##child##ArrType_Type.tp_bases =                                  \
        Py_BuildValue("(OO)", &Py##parent2##ArrType_Type,               \
                      &Py##parent1##_Type);                             \
    if (PyType_Ready(&Py##child##ArrType_Type) < 0) {                   \
        PyErr_Print();                                                  \
        PyErr_Format(PyExc_SystemError,                                 \
                     "could not initialize Py%sArrType_Type",           \
                     #child);                                           \
        return -1;                                                      \
    }                                                                   \
    Py##child##ArrType_Type.tp_hash = Py##parent1##_Type.tp_hash;
    ...
    DUAL_INHERIT(Int, Int, SignedInteger);

Could it be the multiple inheritance that causes the problem here?
History
Date User Action Args
2010-07-20 05:08:43belopolskysetrecipients: + belopolsky, amaury.forgeotdarc, grubert, LambertDW, barronh
2010-07-20 05:08:42belopolskysetmessageid: <1279602522.51.0.80758042755.issue5476@psf.upfronthosting.co.za>
2010-07-20 05:08:39belopolskylinkissue5476 messages
2010-07-20 05:08:38belopolskycreate