Comment 1 for bug 804130

I think I may have seen something like this cause a confusing error when there was a syntax error in code or similar only hit starting the child process.

I think fixing the handles to be close-on-exec where appropriate could be good. Also just having an 'except' block that prints an error and returns 1 would be cheap and worthwhile.