Hi *, *PLEASE*: reply even if you don't care. I cannot tell whether there is silence because nobody (apart from Florian - thanks for the reply!) did read the question, or because just nobody really cares.
Please vote: [ ] OOo should continue to use system python, regardless of problems accessing pyuno from outside OOo [ ] OOo should use internal python, ship with its own copy of python (increases download size) [ ] I don't care - you should do a poll on the user-focused lists instead. For reference, the original mail in fullquote, so you don't have to dig in archives for messagess from a month ago... ciao Christian On Wed, May 19, 2010 at 12:55 PM, Christian Lohmaier <cl...@openoffice.org> wrote: > Hi *, > > as the baseline of Mac OSX 10.4 only ships with python version 2.3, > OOo is compiled against that version. This is not a problem when > running python from within OOo, you can run python macros on > 10.4/10.5/10.6 with no problem with a default installation of Mac OSX. > > There is a big "BUT" however: > On never versions of Mac OSX, it is not possible to run standalone > python with pyuno. I.e. you cannot run python from outside OOo and run > your script. You'll get "incompatible version" style errors. (newer > versions of Mac OSX ship with the 2.3 basic framework, but only have > python2.5 and 2.6 launchers. I failed to get it to "import uno" on > 10.6, no matter what tricks with environment variables I tried. Maybe > there's some trick to get it running, but I gave up. I'm neither a > python nor a Mac user, so there might still be a way though. > (Again: running python macros from within OOo is not a problem, python > loaded via OOo's library gets things right) > > Eric Bachard made me aware on IRC that the python in OOo's sources is > already at 2.6.1 and made me start working on it. For some reason Eric > cut communication after I filed the issues with patches <sigh/>, so I > finished it myself. > > Main issue is http://qa.openoffice.org/issues/show_bug.cgi?id=111496 > Other issues with the corresponding patches can be found in the > depending issues. > > The questions basically are: > Should OOo for Mac ship with internal python? Or should it still use > system-python? > Anyone a python-guru/deep into Apple's Framework stuff who can tell > how to get a "import uno" work on Mac OSX >10.4 from outside OOo? > Anyone into python extensions and want to give internal python 2.6.1 a > thorough test? > Anyone for code-review? > > If necessary, I could provide installsets for PPC (build-OS: 10.4) and > Intel (build-OS: 10.6). > > ciao > Christian > --------------------------------------------------------------------- To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org For additional commands, e-mail: mac-h...@porting.openoffice.org
