[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#717930: ImportError: No module named pyuno



Package: python-uno
Version: 1:4.1.0-1
Severity: important
Tags: patch

Dear Maintainer,

Don't if this is a Debian bug or a LibreOffice bug: haven't found any bug like
this on LibreOffice BTS.

Using Python-uno inside a python virtualenv, starting a python program that
import "uno" library I get this error:
(only relevant rows are printed)

-------------------------------------------------------
Traceback (most recent call last):
  File "./manage.py", line 23, in <module>
    execute_manager(settings)
[...]
  File "/opt/propilei/src/propilei/../propilei/lib/ooolib.py", line 44, in
<module>
    import uno
  File "/opt/propilei/django/lib/python2.7/site-packages/uno.py", line 24, in
<module>
    import pyuno
ImportError: No module named pyuno
-------------------------------------------------------

With the previous version of the package, on another server, python-uno works
fine.

Comparing the /usr/share/pyshared/uno.py with previous version I've noticed the
path on line 2 was missing the leading '/'

sys.path.append('usr/lib/libreoffice/program')

I've added the leading '/' and now everythings works!
Line 2 now looks like:

sys.path.append('/usr/lib/libreoffice/program')

(notice the leading '/' in the path)




-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (700, 'unstable'), (600, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages python-uno depends on:
ii  libc6             2.17-7
ii  libgcc1           1:4.8.1-8
ii  libpython2.7      2.7.5-6
ii  libreoffice-core  1:4.1.0-1
ii  libstdc++6        4.8.1-8
ii  python            2.7.5-2
ii  uno-libs3         4.1.0-1
ii  ure               4.1.0-1

python-uno recommends no packages.

python-uno suggests no packages.

-- no debconf information


Reply to: