Odd problem running command-line python scripts (win2k)

[Brian Kelley]

As another data point, sys.executable reports that the same version of 
python is being run by both executions of the script.

As yet another datapoint, on my windows2000 machine at home (no service 
pack) I get the same behavior except that any system call that runs from 
an imported module

---some_sys_call.py
import os
print os.system("DIR >t")

---caller.py
import some_sys_call

wheras at work (service pack 5) the system call fails.

So I guess I'll label this as "don't do that" except, isn't typing

some_python_prog.py

at the command line the same as double clicking in explorer?  This 
troubles me the most. I'll look into it.

Brian