dev-python/gmpy doesn't work with Python 3.2. It uses PyCObject-related functions which are deprecated in Python 3.1 and removed in Python 3.2. PyCapsule-related functions should be used. http://docs.python.org/3.1/c-api/cobject.html http://docs.python.org/3.1/c-api/capsule.html $ python3.2 -c 'import gmpy' Traceback (most recent call last): File "<string>", line 1, in <module> ImportError: /usr/lib64/python3.2/site-packages/gmpy.so: undefined symbol: PyCObject_FromVoidPtr
Created attachment 214055 [details] gmpy-1.10:20091224-185431.log -Werror=implicit-function-declaration allows to reproduce this bug during building.
http://code.google.com/p/gmpy/source/detail?r=196
gmpy-1.11 is in portage, which compiles fine with python3.
Building of gmpy extension now succeeds, but building of pysymbolicext extension fails. src/pysymbolicext.c: In function ‘initpysymbolicext’: src/pysymbolicext.c:441: error: implicit declaration of function ‘PyCObject_Check’ src/pysymbolicext.c:441: error: implicit declaration of function ‘PyCObject_AsVoidPtr’ src/pysymbolicext.c:441: warning: cast to pointer from integer of different size
since you added gmpy 1.12, is the bug still there?
I updated summary.
ok, it's an incompability. What to do now? Try to fix it, or wait for new upstream release? I can't test/do it, since python 3.2 isn't even in portage yet.
Python 3.2_pre* is available in python overlay.
(I'm the current maintainer of gmpy. I just stumbled across this bug. It wasn't reported upstream.) pysymbolicext.c has been removed from the development version of gmpy 2.x (aka gmpy2) and should have been removed from 1.14. gmpy itself no longer uses PyCObject or PyCapsule functions. Can the compiling of pysymbolicext.c just be removed from the build? If not, would I need to release a new version that removes pysymbolicext.c?
(In reply to comment #9) We thought that pysymbolicext extension is somehow useful. I have now disabled building of this extension.