Bug#479183: python-uno: Python scripting unsupported

[Rene Engelhard <rene@debian.org>]

Hi,

Florian Hatat wrote:
> I cannot execute any Python macro from the OpenOffice process.
> 
> Steps to reproduce:
> 1. drop a file "test.py" in "~/.openoffice.org2/user/Scripts/python/" ("python"
>    may need to be created first). "test.py" could look like the following:
> 
> def someFunction(*args):
>   pass
> 
> 2. launch OOo (writer, calc, doesn't matter which one).
> 
> 3. go to Tools > Macros > Manage macros, and unfold "My macros": only the
>    "Standard" module appears.
>    
> Expected behaviour: there should also be a module named "test" corresponding to
> "test.py" under "My macros".
> 
> I've tried to remove "~/.openoffice.org2/", without success.
> 
> The official build (fetched from http://openoffice.org/) works fine (i.e. there
> is a "test" module).

As I already wrote in my other mail; this is a knwon bug fixed in
2.4.0-6 (the bug was told on IRC to me, where we also did the debugging
which lead to the fix)

> This only affects OOo Scripting Framework (scripts inside OOo process: macros
> and addins): the UNO bridge works fine when Python is directly called from the
> shell (for example "python /usr/share/doc/python-uno/demo/swriter.py" works as
> expected).

Which explains why I didn't notice that myself :-)

Regards,

Rene