[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.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4