Bug 10281 - pyuno is python3.x only
Summary: pyuno is python3.x only
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO, Triaged
Depends on:
Blocks:
 
Reported: 2013-05-25 17:59 CEST by Shlomi Fish
Modified: 2013-06-07 17:11 CEST (History)
0 users

See Also:
Source RPM: libreoffice-4.0.3.3-4.mga4.src.rpm
CVE:
Status comment:


Attachments

Description Shlomi Fish 2013-05-25 17:59:04 CEST
Description of problem:

shlomif[rpms]:$mageia/unoconv$ rpm -q libreoffice-pyuno 
libreoffice-pyuno-4.0.3.3-4.mga4
shlomif[rpms]:$mageia/unoconv$ python
Python 2.7.3 (default, Jan 13 2013, 20:09:12) 
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyuno
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named pyuno
>>> 

shlomif[rpms]:$mageia/unoconv$ rpm -ql libreoffice-pyuno  | grep /usr/lib64/python
/usr/lib64/python3.3/site-packages/uno.py
/usr/lib64/python3.3/site-packages/unohelper.py
shlomif[rpms]:$mageia/unoconv$ 

As you can see - one cannot use pyuno from python 2.x.

Regards,

-- Shlomi Fish

Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-05-25 19:40:32 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => thierry.vignaud

Comment 1 Thierry Vignaud 2013-05-28 20:40:31 CEST
I can switch LO from python2 to python3 (like FC).
It's either one or the other.
WDYT?

Keywords: (none) => NEEDINFO

Comment 2 Shlomi Fish 2013-05-29 18:50:50 CEST
(In reply to Thierry Vignaud from comment #1)
> I can switch LO from python2 to python3 (like FC).

Is Libreoffice python2 now - or is it python 3 now? I don't understand. I want it to be usable from python 2.

Regards,

-- Shlomi Fish 

> It's either one or the other.
> WDYT?
Comment 3 Thierry Vignaud 2013-06-07 17:11:09 CEST
It's python3: we cannot have both.
Since python3 is the future, it's what has been choosen

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.