Message123648
> + "NotImplemented" was printed
Hmm, looks like a compiler bug to me. Can anyone reproduce this on a debug build? In any case, someone with a Windows setup will have to troubleshoot this further.
Note that the code in abstract.c is supposed to convert NotImplemented returns to type errors:
static PyObject *
binary_op(PyObject *v, PyObject *w, const int op_slot, const char *op_name)
{
PyObject *result = binary_op1(v, w, op_slot);
if (result == Py_NotImplemented) {
Py_DECREF(result);
return binop_type_error(v, w, op_name);
}
return result;
}
It should be possible to find out why this is not happening by stepping through this code with a debugger. |
|
Date |
User |
Action |
Args |
2010-12-08 20:39:05 | belopolsky | set | recipients:
+ belopolsky, loewis, ocean-city, brian.curtin |
2010-12-08 20:39:05 | belopolsky | set | messageid: <1291840745.7.0.0338525246955.issue10654@psf.upfronthosting.co.za> |
2010-12-08 20:39:03 | belopolsky | link | issue10654 messages |
2010-12-08 20:39:03 | belopolsky | create | |
|