Hi,
There are some problems with pyuno in OOo3.0.0 (in particular with the
python executable). Here the known problems and the workarounds for the
moment.
Bye,
Joerg
-----------------
1)( unix only), you need to set LD_LIBRARY_PATH correctly before
starting the python executable, eg.
export set
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:../../openoffice.org/ure/lib:../../openoffice.org/basis3.0/program
./python
2) (windows only) The python scripting framework (scripts within
openoffice via Extras/Macro/) does not work (at least for me). The cause
is unknown and under investigation.
3)
(windows only) When you try to connect to a running office process, you get
__main__.com.sun.star.connection.NoConnectException: Connector
couldn't connect to socket (WSANOTINITIALISED, WSAStartup() has not been
called)
You can workaround this, by placing a
import socket
at the top of your script.
4) (windows only) The python program crashes or you get an attribute error
AttributeError: getCurrentComponent (or some other attribute)
This is because the types could not be loaded due to changes in the uno
bootstrapping mechanism. You can work around it for now by setting the
variable set URE_BOOTSTRAP=fundamental.ini
and running python from the
path/to/office/OpenOffice.org 3/programdirectory.
5) (windows only) Interactive mode in python does not work correctly
When you start the python executable without parameters, the interactive
session runs somewhat fuzzy (at least on my machine). When you get the
prompt >>>> , everything you type will be interpreted as a shell
command. When you then just press return, you are prompted with your
current working directory, here you can place a python command. Both
input modes alternate.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
