Apache OpenOffice (AOO) Bugzilla – Issue 24815
pyuno: Importing pyuno fails with _PyImport_FixupExtension
Last modified: 2007-06-18 10:33:00 UTC
After fixing issue #24814: zagy@lrrr:~/OpenOffice.org1.1.0/program> ./python Python 2.2.2 (#1, Oct 5 2003, 21:06:14) [GCC 3.3 20030304 (Apple Computer, Inc. build 1435)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import uno Traceback (most recent call last): File "<stdin>", line 1, in ? File "uno.py", line 62, in ? import pyuno SystemError: _PyImport_FixupExtension: module pyuno not loaded >>> And yes, I read the FAQ. I made absolutely sure it's using the right version. If it's not using the right version the error is quite another one actually. This is OOo_1.1.0_031006_MacOSX_install_en.tar.gz on Panther.
Hi, This should already be fixed in 1.1.1a for MacOSX. Kevin
There are no binary packages for this, are there?
Joerg, please help with this one as well.
Hi, resolving this as fixed. Kevin
I'd like to re-open. On Debian unstable I get, with a 3-line shell script named "sopy": $ sopy + export PYTHONPATH=/usr/local/stow/OpenOffice.org1.1.3/program:/usr/local/stow/OpenOffice.org1.1.3/program/python-core-2.2.2/lib + PYTHONPATH=/usr/local/stow/OpenOffice.org1.1.3/program:/usr/local/stow/OpenOffice.org1.1.3/program/python-core-2.2.2/lib + export PYTHON=/usr/local/stow/OpenOffice.org1.1.3/program/python-core-2.2.2/bin/python + PYTHON=/usr/local/stow/OpenOffice.org1.1.3/program/python-core-2.2.2/bin/python + exec /usr/local/stow/OpenOffice.org1.1.3/program/python-core-2.2.2/bin/python Python 2.2.2 (#1, Jul 21 2003, 15:13:13) [GCC 3.2.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import uno Traceback (most recent call last): File "<stdin>", line 1, in ? File "/usr/local/stow/OpenOffice.org1.1.3/program/uno.py", line 62, in ? import pyuno SystemError: _PyImport_FixupExtension: module pyuno not loaded >>> import uno >>> Ie, it works ok on the second 'import', but crashes on the first. Fwiw, my system Python is 2.3.4 and not 2.2.2, whereby you can verify that I call the correct python, contrary to FAQ #3: $ python Python 2.3.4 (#2, Nov 13 2004, 18:58:41) [GCC 3.3.5 (Debian 1:3.3.5-2)] on linux2
Hi, what gives ./python ? Maybe the macos equivalent of the LD_LIBRARY_PATHdoes not contain a '.' or so. > Ie, it works ok on the second 'import', but crashes on the first. Is pyuno functional afterwards ? Bye, Joerg
This issue has been "RESOLVED" for quite a time, I assume I can close it ...