Bug#572064: Please provide python-uno for other python version, at least 2.6
Hi,
On Tue, Mar 02, 2010 at 12:45:26PM +0100, Jürgen Strobel wrote:
> Ok here we are at the root of the problem. I do *not* want another
> python interpreter inside OOo. I fully understand there's only one, and
> that's the debian default version.
Aha. Then use python2.5 and be done.
> I want the necessary UNO libs to access the UNO bridge from the outside,
> from a different python interpreter than running inside OOo, even from a
> different version.
Maybe it is. Don't know, and neither do I really care. If you deploy
such a think you have a controlled environment. And when that environment
mandates 2.5, so be it. (Or you rebuild OOo against 2.6)
> After all it should be possible from java or any
> other language too, even networked from other hosts.
I don't think that Java is a proper example.
> In short I wanted the following to work with python2.6:
>
> ~/% python
> Python 2.5.5 (r255:77872, Feb 1 2010, 19:53:42)
> [GCC 4.4.3] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import uno
> >>> uno.getComponentContext()
> pyuno object (com.sun.star.uno.XComponentContext)0x96e9d88{,
> supportedInterfaces={com.sun.star.uno.XComponentContext,com.sun.star.container.XNameContainer,com.sun.star.lang.XTypeProvider,com.sun.star.uno.XWeak,com.sun.star.lang.XComponent}}
>
> If this is not possible I feel UNO fails miserably at its design goal.
> What good is a bridge if I can't access it without linking against the
> exact same software running on the other side?
You know that "proper" OOo embeds a full copy of python in their installation
set so you don't have any choice except using their python binary?
Or on Mac OS they also just use their default python.
Similar thing here.
This is not even supported upstream. Though, no idea whether accessing
it with an other python would work - I surely will not "waste" my time
getting this to work.
> Maybe you could split the package providing the python loader for inside
> OOo and the UNO bindings for system python. Maybe the python guys should
> provide the bindings and a separate UNO client lib for each python version.
Maybe I could, but I surely won't just for some people who want to
use the non-default python. (Besides that, that probably will just
result in a circular dependency)
Grüße/Regards,
René
--
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' rene@debian.org | GnuPG-Key ID: D03E3E70
`- Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70
Reply to: