Question

I have the following post-build step in a VC++ 2005 project that calls a Python 2.5.1 script:

postbuild.py 

postbuild.py does:

import os os.system('cd') # cd is just a test, could be anything 

The process never starts, and it’s the same with any other process I try, even using subprocess.call or Popen instead of os.system.

Does anyone know about anything related to problems like this in Python 2.5.1 or in build events in Visual C++ 2005 SP1?

Answer 1

Solved. For some reason, using ‘postbuild.py’ as postbuild step inhibits the python script from spawning other processes, where ‘python.exe postbuild.py’ has no problems, and neither ‘pythonw.exe postbuild.py’. I’m not sure why this happens, as all three methods are valid when used from cmd.exe.

But I would like to know if anyone has an explanation for this.