[MERGE][bug 276868] Blacklist pyrex

Matt Nordhoff mnordhoff at mattnordhoff.com
Wed Oct 1 23:44:42 BST 2008

John Arbash Meinel wrote:
> It seems that pyrex fails to properly compile the new iter_changes
> code that Robert wrote. The code it generates re-uses a "local" pointer and
> calls "PY_DECREF" after having set it to NULL. (It mixes PY_XDECREF which is
> NULL safe with PY_DECREF which is not.)
> This just adds an explicit blacklist for all pyrex compilers < for that
> extension.
> One alternative is to set "have_pyrex = False" instead, and issue a note that
> we won't generate any of the .c files for old versions of pyrex.
> For now, this was the "minimal" change I could do.
> Thoughts?
> John
> =:->

Hey, I'm on Pyrex (Gutsy, yes I'm lazy) and don't have any
problems (aside from some compiler warnings). Why are you blacklisting it?

(OTOH, I've never *tested* btrees.. Hmm..)

More information about the bazaar mailing list