Check Pyrex 0.9.9 support

[GoogleCodeExporter]

http://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/version/Doc/Release_Not
es_0.9.9.html

Original issue reported on code.google.com by the.good...@gmail.com on 12 Apr 2010 at 1:12

[GoogleCodeExporter]

I got this error message and failed to compile pygr. It is related to pyrex 
0.9.9 "not None" feature.

pyrexc pygr/cdict.pyx --> pygr/cdict.c
/home/deepreds/big_kobic_kr/pygr-0.8.1/pygr/cdict.pyx:95:4: __new__ method of 
extension type will change semantics in a future version of Pyrex. Use 
__cinit__ instead.
/home/deepreds/big_kobic_kr/pygr-0.8.1/pygr/cdict.pyx:160:4: __new__ method of 
extension type will change semantics in a future version of Pyrex. Use 
__cinit__ instead.
/home/deepreds/big_kobic_kr/pygr-0.8.1/pygr/cdict.pyx:212:4: __new__ method of 
extension type will change semantics in a future version of Pyrex. Use 
__cinit__ instead.
/home/deepreds/big_kobic_kr/pygr-0.8.1/pygr/cdict.pyx:261:4: __new__ method of 
extension type will change semantics in a future version of Pyrex. Use 
__cinit__ instead.
/home/deepreds/big_kobic_kr/pygr-0.8.1/pygr/cdict.pyx:407:4: __new__ method of 
extension type will change semantics in a future version of Pyrex. Use 
__cinit__ instead.
/home/deepreds/big_kobic_kr/pygr-0.8.1/pygr/cdict.pyx:212:22: Warning: 'not 
None' will become the default in a future version of Pyrex. Use 'or None' to 
allow passing None.

Original comment by deepr...@gmail.com on 15 Nov 2010 at 7:17

[GoogleCodeExporter]

I've looked into this and it seems the problem is that the "use __cinit__ 
instead of __new__" warning has been upgraded to an error. Decided to address 
the "not None" warning even so. Both changes have been made in my "pyrex099" 
branch and I have let Chris know about them so that they can be merged into the 
official tree.

Original comment by mare...@gmail.com on 29 Jun 2011 at 12:53

• Changed state: FixedNeedsReview