[ python-Bugs-1156179 ] Calls from VBScript clobber passed args
SourceForge.net
noreply at sourceforge.net
Fri Sep 1 23:08:41 CEST 2006
Bugs item #1156179, was opened at 2005-03-03 15:42
Message generated for change (Comment added) made by rupole
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1156179&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Windows
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Erik Rose (grincheroo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Calls from VBScript clobber passed args
Initial Comment:
I'm using Python 2.4.0 and VBScript under ASP on IIS 5. If I call a
Python function from VBScript AND pass a local var as the first
parameter AND don't use the return value, then the local var I
passed in is, upon the function's return, set to Null.
If I store the return value (even if there isn't one) OR pass the return
value to another function, this doesn't happen. I'm attaching some
snippets that demonstrate and work around the bug.
----------------------------------------------------------------------
Comment By: Roger Upole (rupole)
Date: 2006-09-01 16:08
Message:
Logged In: YES
user_id=771074
I think this is actually a vbscript behaviour. If not,
it's a bug in Pywin32's Active Scripting implementation.
Either way, this shoud probably be closed as third-party.
----------------------------------------------------------------------
Comment By: Erik Rose (grincheroo)
Date: 2005-03-08 10:41
Message:
Logged In: YES
user_id=888812
Let me refine the description a bit: the bug doesn't clobber only a local var
passed as the *first* param; it clobbers the first local var passed, whether
it's the first param or not. For example,
call go(x)
clobbers x, as I've said before, but...
call aTwoParamFunction("somethingStatic", x, y)
clobbers x as well! y is not clobbered.
----------------------------------------------------------------------
Comment By: Erik Rose (grincheroo)
Date: 2005-03-08 10:39
Message:
Logged In: YES
user_id=888812
Let me refine the description a bit: the bug doesn't clobber only a local var
passed as the *first* param; it clobbers the first local var passed, whether
it's the first param or not. For example,
call go(x)
clobbers x, as I've said before, but...
call aTwoParamFunction("somethingStatic", x, y)
clobbers x as well! y is not clobbered.
----------------------------------------------------------------------
Comment By: Erik Rose (grincheroo)
Date: 2005-03-08 10:39
Message:
Logged In: YES
user_id=888812
Let me refine the description a bit: the bug doesn't clobber only a local var
passed as the *first* param; it clobbers the first local var passed, whether
it's the first param or not. For example,
call go(x)
clobbers x, as I've said before, but...
call aTwoParamFunction("somethingStatic", x, y)
clobbers x as well! y is not clobbered.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1156179&group_id=5470
More information about the Python-bugs-list
mailing list