[issue1524] os.system() fails for commands with multiple quoted file names

qiang <[EMAIL PROTECTED]> added the comment: in subprocess.py , change line 788: args = comspec + " /c " + args to: args = comspec + args it will be ok. -- nosy: +likes ___ Python tracker <[EMAIL PROTECTED]>

[issue1524] os.system() fails for commands with multiple quoted file names

daniel.weyh <[EMAIL PROTECTED]> added the comment: Got similiar problem. Think it's a thing with the pipe '>'. Try calling the windows-shell (e.g. C:\WINDOWS\system32\cmd.exe) with '/C' and your comman dline after that (in quotes). > subprocess.call(r'C:\WINDOWS\system32\cmd.exe /C "YourCommand

[issue1524] os.system() fails for commands with multiple quoted file names

Sean Reifschneider <[EMAIL PROTECTED]> added the comment: I would agree with Georg that there isn't anything we can do about this. I had someone try from the Windows XP command shell and: "dir" "/w" reports that it can't run the combined command, where: dir /w works just fine. My conclusions ar

[issue1524] os.system() fails for commands with multiple quoted file names

Jean-François Bastien added the comment: I confirm the problem. To resolve it try: os.system('call "TheCommand" > "MyOutput"') -- nosy: +jfbastien __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1524] os.system() fails for commands with multiple quoted file names

Christian Heimes added the comment: Yes, it's necessary whenever the command part contains a space or other special characters. __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1524] os.system() fails for commands with multiple quoted file names

Rafael Zanella added the comment: I don't have access to a Windows machine, but is it really necessary to quote the command part? I mean, on GNU/Linux if you pass a command wich has spaces , say e.g.: ls -lah, quoted it fails too, but if passed without quotes it runs just fine. -- nosy:

[issue1524] os.system() fails for commands with multiple quoted file names

Guy Mott added the comment: > Are you sure that the exact command line works in a Windows shell? Yes, I tried running the exact same command line in a Windows shell and it worked fine. Note that the buggy.py script echoes the command line and then immediately calls os.system with it. E.g.:

[issue1524] os.system() fails for commands with multiple quoted file names

Georg Brandl added the comment: Are you sure that the exact command line works in a Windows shell? Python does no processing on the string, it just hands it to the platform system() function, so if MS decided that to work different from a command prompt there's nothing we can do about.

[issue1524] os.system() fails for commands with multiple quoted file names

Christian Heimes added the comment: I don't think that we can do anything about your problem. The user of os.system() is responsible to do the quoting himself. os.system() is just a tiny wrapper around the low level C function. We don't plan to chance the fact that os.system() doesn't handling qu

[issue1524] os.system() fails for commands with multiple quoted file names

New submission from Guy Mott: Given a call to os.system() with a command string like this: os.system('"TheCommand" > "MyOutput"') # fails then the call fails with the following error message on the console: 'TheCommand" > "MyOutput' is not recognized as an internal or external command,