@white ![:D]( "Very Happy")
I think you have hit the problem right on target.
If I pass the whole path of ..../python/python.exe + script_name.py in the command box then it works exactly as you said. It passes the long path perfectly to the script.
Obviously it can't guess what bit version a script by itself is. However this issue does not exist for passing to .bat script files even without calling CMD first - which still seems odd.
If I add "python.exe" on it's own I suspect TC is guessing the wrong bit version of my 64bit Python unless a full path is set.
Maybe it's an XP legacy thing.
Anyway that is useful information white'. Thanks you.
I can now mark this issue: SOLVED! Thanks to you White'![:D]( "Very Happy")
I think you have hit the problem right on target.
If I pass the whole path of ..../python/python.exe + script_name.py in the command box then it works exactly as you said. It passes the long path perfectly to the script.
Obviously it can't guess what bit version a script by itself is. However this issue does not exist for passing to .bat script files even without calling CMD first - which still seems odd.
If I add "python.exe" on it's own I suspect TC is guessing the wrong bit version of my 64bit Python unless a full path is set.
Maybe it's an XP legacy thing.
Anyway that is useful information white'. Thanks you.
I can now mark this issue: SOLVED! Thanks to you White'
Statistics: Posted by Pumpkin — 2024-12-29, 14:05 UTC