[Python-Dev] test_popen broken on Win2K
Tim Peters
tim.one@comcast.net
Fri, 07 Mar 2003 17:02:23 -0500
Fri, 07 Mar 2003 17:02:23 -0500
- Previous message: [Python-Dev] test_popen broken on Win2K
- Next message: [Python-Dev] test_popen broken on Win2K
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Thomas Heller] > ... > In distutils we had a similar problem. I don't remember the details > at the moment exactly, but I think enclosing sys.executable in double > quotes *only* when it contains spaces should do the trick. That's what I checked in, but doubt it works in general. The cmdline test_popen passes to cmd.exe would have 4 double-quote characters then, and the docs I quoted clearly say it falls into the second case then (so it would strip the first and last quotes, leaving the second and third, which don't make sense anymore). The trick would work if the executable path were the only quoted thing on the cmdline.
- Previous message: [Python-Dev] test_popen broken on Win2K
- Next message: [Python-Dev] test_popen broken on Win2K
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]