CVXOPT doesn't work with Python3 (KUBUNTU 11.04)

163 views
Skip to first unread message

dmitrey

unread,
May 8, 2011, 5:54:50 AM5/8/11
to CVXOPT
hi all,
I've compiled and installed CVXOPT with Python3 and got the following
error:

/usr/local/lib/python3.2/dist-packages/cvxopt/base.cpython-32mu.so:
undefined symbol: PyCObject_FromVoidPtr

there is some info in google, like this one
http://stackoverflow.com/questions/1547310/python-3-1-1-with-enable-shared-will-not-build-any-extensions

but it's not clear which makefile has to b fixed. Could you fix it in
your sources?

I have KUBUNTU 11.04.

Regards, D.

Max

unread,
May 25, 2011, 2:40:36 PM5/25/11
to CVXOPT
I have a similar issue using Mac OS X10.6 and python 3.2:
Compiling/installing works fine, but when trying to import the module
I get the following error:

Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/Library/Frameworks/Python.framework/Versions/3.2/lib/
python3.2/site-packages/cvxopt/__init__.py", line 31, in <module>
import cvxopt.base
ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/3.2/
lib/python3.2/site-packages/cvxopt/base.so, 2): Symbol not found:
_PyCObject_FromVoidPtr
Referenced from: /Library/Frameworks/Python.framework/Versions/3.2/
lib/python3.2/site-packages/cvxopt/base.so
Expected in: dynamic lookup

Max



On May 8, 2:54 am, dmitrey <dmitrey.kros...@scipy.org> wrote:
> hi all,
> I've compiled and installed CVXOPT with Python3 and got the following
> error:
>
> /usr/local/lib/python3.2/dist-packages/cvxopt/base.cpython-32mu.so:
> undefined symbol: PyCObject_FromVoidPtr
>
> there is some info in google, like this onehttp://stackoverflow.com/questions/1547310/python-3-1-1-with-enable-s...

Dan Miller

unread,
Oct 17, 2011, 4:11:23 AM10/17/11
to cvx...@googlegroups.com
Late reply, but I had the same problem. I'm guessing this is due to the removal of the CObjects package in Python 3.2. Here's a discussion from the Python mailing list about updating obsolete code:

http://mail.python.org/pipermail/python-list/2011-March/1268402.html

So updating for Python 3.2 compatibility will likely require a source code change.

Reply all
Reply to author
Forward
0 new messages