| Summary: | pyuno is not in the PYTHONPATH | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jonathan Serafini <delerious010> |
| Component: | New packages | Assignee: | Gentoo Office Team <office> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | enhancement | ||
| Priority: | Lowest | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Jonathan Serafini
2006-10-30 04:36:57 UTC
What is the actual problem here, or: What do we gain by doing this? Sorry about the lack of details ... By adding /usr/lib/openoffice/program to PYTHONPATH, or by moving all python related modules to /usr/lib/python2.4/site-packages/openoffice, you will effectively be adding the openoffice python modules to python's search path. This will allow you to load the uno module without having to manually tweak python's search path. This seems to be more inline with the way other packages function. For instance, avahi installs all it's python modules into : /usr/lib/python2.4/site-packages/avahi And samba does likewise by adding them to : /usr/lib/python2.4/site-packages/samba This isn't by any means mission critical, it's just one of those "it would be nice if things just worked" things. Have you checked it? Will doing so allow both python scripting from within openoffice to work as well as external openoffice access through openoffice (without having to start OOo)? See last comment by Paul, atm I'm just not seeing the real life gain we get, if you get some more answers to this, please re-open. |
