Comment 3 for bug 276868

Trying to debug the pyrex output, it appears that it sometimes does:

PY_XDECREF(pointer); pointer = 0;

and then later does

PY_DECREF(pointer).

So it seems we are just triggering a bug in pyrex 0.9.4.1. Further, it seems to only happen because the functions are long and complex enough that it re-uses some of its temporary variables.

There doesn't seem to be an easy way to work around this, so instead we'll just blacklist that version of the compiler. It won't effect released versions, because we always bundle the .c files anyway.