[framework-issues] [Issue 54155] python : g_exportedScript s interpreted within commented line

2006-01-11 Thread jbu
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

Status|UNCONFIRMED   |RESOLVED

Resolution|  |FIXED





--- Additional comments from [EMAIL PROTECTED] Wed Jan 11 14:12:55 -0800 
2006 ---
fixed on cws_src680_pyunofixes2. Fixed it by checking for a linefeed at the end
of the code.

I can't use execfile, because the module might not be reachable via a systempath
(e.g. when the module is stored in a document).

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
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]



[framework-issues] [Issue 54155] python : g_exportedScript s interpreted within commented line

2005-11-10 Thread douardda
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
script insead of the exec one.

David

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
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]



[framework-issues] [Issue 54155] python : g_exportedScript s interpreted within commented line

2005-11-06 Thread jbu
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 
python exec statement, e.g. start python and do the following

--
Python 2.3.4 (#53, Jul  2 2004, 22:10:14) [MSC v.1200 32 bit (Intel)] on win32
Type help, copyright, credits or license for more information.
 exec 'def f():\n\tpass\n#'
Traceback (most recent call last):
  File stdin, line 1, in ?
  File string, line 3
#
^
SyntaxError: invalid syntax
 exec 'def f():\n\tpass\n#\n'
 
-
The syntax error is not given, when you import such a file, so python sadly 
does something more than just evaluating the code :-(.

I think, I will work around this by adding a line feed when the code does not 
end with one.

Joerg


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
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]



[framework-issues] [Issue 54155] python : g_exportedScript s interpreted within commented line

2005-11-06 Thread bmarcelly
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 
assignment.

No need to test the string, adding systematically \n to the string will go 
around the 
bug...
  Bernard

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
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]



[framework-issues] [Issue 54155] python : g_exportedScript s interpreted within commented line

2005-09-19 Thread npower
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

   Assigned to|npower|jbu





--- Additional comments from [EMAIL PROTECTED] Mon Sep 19 04:17:34 -0700 
2005 ---
reassign

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
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]



[framework-issues] [Issue 54155] python : g_exportedScript s interpreted within commented line

2005-09-18 Thread bmarcelly
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 is followed by at least 
one blank 
line there is no error, and the variable is interpreted although it is in a 
commented 
line ...

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
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]