[MERGE][bug 276868] Blacklist pyrex 0.9.4.1

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matt Nordhoff wrote:
> John Arbash Meinel wrote:
>> It seems that pyrex 0.9.4.1 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 <0.9.6.0 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 0.9.5.1a-1 (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..)

I can ratchet it back. I believe 0.9.5 works fine. Mostly I only know that
0.9.4.1 is segfaulting with bzr.dev. I thought I'd play it safe, but I don't
have to play it that safe.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI4/4tJdeBCYSNAAMRAg7rAJ9+RY+lTiewr/AJk8l6XXGi/CH5vACbBUyO
YklZnvTsFZ1ZmbWg9LYzfnk=
=D/jE
-----END PGP SIGNATURE-----