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 theller
Recipients ajaksu2, facundobatista, theller
Date 2008-04-02.18:47:15
SpamBayes Score 0.024212267
Marked as misclassified No
Message-id <1207162038.42.0.208443122783.issue2534@psf.upfronthosting.co.za>
In-reply-to
Content
Running Daniels code interactively, with a debug build on Windows,
additionally prints 'XXX undetected error' before the Runtime error is
raised.

I cannot see anything that is wrong with my code.  Maybe this, and the
test failure, has to do with the fact that the new
'type___subclasscheck__' function is sometimes called with the error
indicator already set?  Maybe some PyErr_Fetch() and PyErr_Restore()
calls are needed inside this function, similar to what
PyObject_IsSubclass() does?  I must admit that I do not really
understand the purpose of these calls...

Anyway, I attach a new, cleaner patch although this one still behaves in
the same, buggy, way: type_instancecheck-2.diff.
History
Date User Action Args
2008-04-02 18:47:18thellersetspambayes_score: 0.0242123 -> 0.024212267
recipients: + theller, facundobatista, ajaksu2
2008-04-02 18:47:18thellersetspambayes_score: 0.0242123 -> 0.0242123
messageid: <1207162038.42.0.208443122783.issue2534@psf.upfronthosting.co.za>
2008-04-02 18:47:17thellerlinkissue2534 messages
2008-04-02 18:47:17thellercreate