Issue 92413

@ jbu: Is this something for you?

Sorry? I don't understand.

I've just noticed, that the version, which is currently included in OOo 3.0 Beta
2 is simply outdated.

What is it that you don't understand? As you can see in
http://wiki.services.openoffice.org/wiki/OOoRelease30 we have had code freeze
for OOo3. So this is targeted for the next release.

"@ jbu: Is this something for you?"

That is, what I don't understand :)

"As you can see in
http://wiki.services.openoffice.org/wiki/OOoRelease30 we have had code freeze
for OOo3. So this is targeted for the next release."

That means, that it is already planned?

'jbu' is the abbreviation of the username of the developer who has brought
python to OOo. AFAIK in it not planned yet.

Oh, I see, ...
Would it make sense to write him a personnel message?

I need this too, because some improvements of the newest version are very useful
and I don't want to have Python installed twice on my system.

I don't think, that it would be that expensive simply to include the newest
Python build into the installer. Or am I wrong and there are also a few
compatibility tasks to do?

Hi,

unfortunately, it is too much work for me atm. 

This is  a very platform dependent task, because every platform needs a special
set of patches, which must be reapplied to the new python version, so the one
doing the job needs to communicate a lot with other community members to get
this done.

I flag this issue as later, as I currently can't say when this issue is started. 

Bye,

Joerg

Hello and thanks for your response!

That's no problem.
The important thing is, that it will be done at some point.
When is secondary for now. :)

I just want to add that this is also a problem for Bibus, a bibliography
programm that works together with OOO. The newer versions of Bibus work with
Python 2.5 and these cannot be used with OOO

jbu: please note
http://svn.gnome.org/viewvc/ooo-build/trunk/patches/dev300/pyuno-python-2.6-uno-import.diff?revision=14748&view=markup
(which afais is needed for python 2.6).

But you either need to make this conditional of also change configure.in to
require python >= 2.6

Where can I find the new patch that needs to be QA and approved?

arbraini: there is none... Even if there was, it'd not be completely representable
with a diff :-)

jbu: any status on this? I see a python26 cws created but that afair didn't get
any commits yet and you didn't reply to my hint for an additional patch needed.

(and why is this issue still on RESOLVED - LATER when there's a cws with this
cws assigned in "new", isn't it STARTED then?)

.

jbu: I felt free to commit the AM_PATH_PYTHON([2.2]) -> AM_PATH_PYTHON([2.6])
and the diff from the link I posted into the python26 cws...

.

+me on CC

@jbu : as I wrote you, I'll test on Mac OS X what has to be done, and if I can, I'll provide patches and/or 
help

(this is sent additionally sent to dev@porting.openoffice.org)

Hi,

the cws python26 (based on DEV300_m41) shall upgrade the python engine from
2.3.4->2.6.1.

In its current state, it builds on linux-x86+win32-xp(with VC++ 9.0 
Express Edition).

I would welcome any porter to support the effort for the other platforms.

Up to now, Eric Bachard aleady agreed to take care for the macos-x port. 

Find below a small description, what needs to be done.

Bye,

Joerg
-----------

what needs to be done:
* checkout python26 cws
* configure ( PYTHONHOME env variable is removed from set_soenv.in)
* in case you reuse a dev300_m41 original build, ensure, that all python stuff
is erased from solver (python.exe, inc/python, lib/python, etc.) otherwise you
will get strange errors
* build the cws. You will probably get problems during building the python
module. Solve them.
* after that, build the rest (you may get additional problems in the pyuno
module, solve them)
* QA-1: 
build the testtools module and switch to testtools/source/bridgetest/pyuno and run

dmake runtest

* QA-2:
install the office, start python from the program directory and type 

import uno

* QA-3:
Start the office, choose Tools/Macros/Run macro ..., click on "OpenOffice.org
Macros", you should then have a pythonSamples Library at the bottom of the list. 

That's it. In case you have any problems you can't solve, let us know either on
this list or within the above issue. Attach patches to the above issue.

@jbu : thanks for the instructions : I'm checkout out the cws and I'll start.  

I'm so sorry for the delay, but I'm awfully busy with my day job these times :/

Fixes for Solaris (unxsoli4.pro, unxsols4.pro, at least with Hamburg setsolar
environment) committed:

cws/python26/python/Python-2.6.1.patch@270927:
- declaring gethostname in pyport.h is not necessary at least on Solaris 10,
conflicts with the declaration in unistd.h (second arg. int vs. size_t), and
would hence break the build in pyuno
- copied the configure BLDLIBRARY stuff from Python-2.3.4.patch (other
Solaris-specific changes in Python-2.3.4.patch appear to no longer be necessary)

cws/python26/python/makefile.mk@270927:
- -xc99=all appears to no longer be necessary, but instead would now break the build

cws/python26/testtools/source/bridgetest/pyuno/makefile.mk@270927:
- necessary adaptions for USE_SHELL=bash

QA-2 and QA-3 (<#desc19>) work fine.  However, QA-1 fails for me with

---8<---
cd ../../../unxsoli4.pro/lib && export
FOO=file:///home/sb/python26/DEV300/ooo/testtools/source/bridgetest/pyuno/../../../unxsoli4.pro/lib
    UNO_TYPES=pyuno_regcomp.rdb UNO_SERVICES=pyuno_regcomp.rdb && python main.py
Traceback (most recent call last):
  File "main.py", line 31, in <module>
    import uno
ImportError: No module named uno
dmake:  Error code 1, while making 'runtest'
---8<---

unxlngi6.pro (gcc 3.4.1) builds and survives QA-2 and QA-3. QA-1 breaks with the
error mentioned by sb.
committed some small pyuno changes regarding PyTypeObject initialisation from
DEV300 (new member 2.3->2.6) to remove gcc warnings.

@hjs,sb:about the qa-1-check, your PYTHONPATH environment variable should
contain a .../solver/300/unxsoli4.pro/lib/pyuno directory, which should contain
a uno.py (which has been delivered before from pyuno module). Please check this
 ... 

@jbu:  indeed,

$ cd $SRC_ROOT/testtools/source/bridgetest/pyuno &&
PYTHONPATH=${PYTHONPATH+${PYTHONPATH}:}$SOLARVERSION/$INPATH/lib$UPDMINOREXT:$SOLARVERSION/$INPATH/lib$UPDMINOREXT/pyuno:.
dmake runtest

makes QA-1 pass for me (where PYTHONPATH was originally unset)

the PYTHONPATH fiddling I described in <#desc24> is due to issue 101213

set target 3.1

@joerg: any work left to do for the upgrade, I suggest to mark issue now as fixed.

*** Issue 71327 has been marked as a duplicate of this issue. ***