Message193503
> Raised by what?
The test raising the assertion error is a Python authorizer callback which returns a Python int (2**32) larger than a C int (> INT_MAX) and so an OverflowError is raised in the C authorizer callback.
> Are you sure you don't just need to clear the exception
> if the callback function raises one?
I read the code one more time, and I saw this:
if (_enable_callback_tracebacks) {
PyErr_Print();
} else {
PyErr_Clear();
}
So it is expected that the C authorizer callback clears the error.
Here is a new patch which implement the same behaviour on _PyLong_AsInt() failure. |
|
Date |
User |
Action |
Args |
2013-07-22 06:24:03 | vstinner | set | recipients:
+ vstinner, ned.deily, r.david.murray, python-dev |
2013-07-22 06:24:03 | vstinner | set | messageid: <1374474243.72.0.791755853424.issue18519@psf.upfronthosting.co.za> |
2013-07-22 06:24:03 | vstinner | link | issue18519 messages |
2013-07-22 06:24:03 | vstinner | create | |
|