incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexandro Colorado <>
Subject Re: Python
Date Thu, 02 Aug 2012 12:38:46 GMT
The issue was written on the UDK site explaining this issue.

I already have python installed on my system, why does the office ship
another python ?

Python itself is shipped with, because
 python must have been compiled with the same C++ compiler as the
office itself on all platforms that use the gcc compiler (e.g. Linux,
BSD, etc.).
 On most Unix platforms, no python shared libraries are available by
default (though some distributions do so). This would have meant, that
python UNO components cannot be executed within the office process.
 Python component developers need a guaranteed minimum platform which
they can rely on.
 Recognition of a python runtime at the installation system would have
been an extremely difficult and time consuming task becausemany
different python installation schemes exist.
Packagers of will create their own packages, for
example redhat or debian, without Python. The standard distribution
must run on low end systems.

Can I use system's python installation ?
 See  here. (

Basically is a lack of support, some dev hours could permanently fix
this issue. But someone needs to do it.

On 8/2/12, Andre Fischer <> wrote:
> Hi all,
> Can anybody remind me of why we bring our own Python?
> Are the reasons still valid after the update to 2.7.3?
> I just updated main/external_deps.lst to load the tarball from
> and had almost chosen the windows binary instead of the
> source tarball.  I am now wondering why we don't have a build
> prerequisite on a pre-installed, standard Python.
> Thanks,
> Andre

Alexandro Colorado EspaƱol

View raw message