Hi,
have a look in
/path/to/ooo/program/pythonscript.py
, replace
LogLevel.use = LogLevel.NONE
with
LogLevel.use = LogLevel.DEBUG
There are also currently undocumented environment variables, which tell
the pyuno bridge to log every call, set therefor the environment variable
export PYUNO_LOGLEVEL=ARGS
, the output is a little hard to read, but helpful during development.
This holds for unix, for windows you need some more switches and the
output gets written to files (no stdout on windows :-( ).
Some error messages still don't appear in these logs, this will improve
in near future (cws pyunofixes4). Once the cws is integrated, I will
document these switches on the official pyuno site.
Bye,
Joerg
Marc Chantreux wrote:
Hi all,
i'm a newbie in python as well as in ooo programming is i make a lot of
mistakes in my code for the moment.
When an error appears in my script, ooo just stops to interpret python
without telling anything on stderr. I haven't noticed a verbose mode or
something like that.
Any clue?
regards,
Marc Chantreux
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
