[pywin32-bugs] [ pywin32-Bugs-3238774 ] Calls from VBScript clobber passed args

[SourceForge.net <no...@so...>]

Bugs item #3238774, was opened at 2011-03-23 17:20
Message generated for change (Tracker Item Submitted) made by lambacck
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3238774&group_id=78018

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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Chris Lambacher (lambacck)
Assigned to: Nobody/Anonymous (nobody)
Summary:  Calls from VBScript clobber passed args

Initial Comment:
I am running into a bug that was submitted erroneously to the python language bug tracker: http://bugs.python.org/issue1156179

I am using v216 with Python 2.6.

The original reporter did some excellent detective work on what is happening. From his description:

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.

He later updates the problem to be:
call go(x)
clobbers x, as I've said before, but...

call aTwoParamFunction("somethingStatic", x, y)
clobbers x as well! y is not clobbered.

If someone can point me in the general right direction, I am willing to try and fix the bug, but as of right now the active script stuff looks like a maze of twisty little passages, all alike.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3238774&group_id=78018