To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=54155
User jbu changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=54155
--- Additional comments from [EMAIL PROTECTED] Thu Nov 10 04:15:52 -0800
2005 ---
IMHO, this should be fixed by using the "execfile" statement in pythonloader.py
scr
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=54155
--- Additional comments from [EMAIL PROTECTED] Sun Nov 6 11:57:38 -0800
2005 ---
Strange error, indeed. It does not happen with a string containing a simple
assign
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=54155
--- Additional comments from [EMAIL PROTECTED] Sun Nov 6 05:23:55 -0800
2005 ---
Hi,
seems to me to be a bug (or a strange behaviour) in python itself. I use the
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=54155
User npower changed the following:
What|Old value |New value
=
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=54155
--- Additional comments from [EMAIL PROTECTED] Sun Sep 18 05:21:01 -0700
2005 ---
Still reproduced on 1.9.130
Note that if the commented-out g_exportedScripts line i
