That's pretty mysterious. The gufunc code does always do clearfperr -> run the loop and stuff -> getfperr. So I don't see how changing getfperr could make new errors suddenly appear. Needs more debugging. I can't easily see that commit's history, but if it includes your other error-object related changes then that could be related, since this error is being raised by an error object callback.