Michael Hudson wrote: > > Robin Becker <robin at jessikat.fsnet.co.uk> writes: > > > no I was testing for another possible value and when that fails I > > try a secondd argument type; I just didn't realise that PyArg_Parse > > would barf if an error was already set. > > This is because there's no way to tell from the return value of > PyDouble_FromDouble whether an error has occurred, so the code for > PyArg_Parse has to check PyError_Occurred. But then again: _any_ API may barf if it gets called while an exception is set. You get similar troubles if you set an exception but don't return NULL to Python. So I think it's good advice to _always_ do PyErr_Clear() after you ignore an exception. Just
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4