subprocess.call using string vs using list

by

subprocess‘s rules for handling the command argument are actually a bit complex.

From the docs:

args should be a sequence of program arguments or else a single string. By default, the program to execute is the first item in args if args is a sequence. If args is a string, the interpretation is platform-dependent and described below. See the shell and executable arguments for additional differences from the default behavior. Unless otherwise stated, it is recommended to pass args as a sequence…. If shell is True, it is recommended to pass args as a string rather than as a sequence.

With shell=False:

On Unix, if args is a string, the string is interpreted as the name or path of the program to execute. However, this can only be done if not passing arguments to the program.

On Windows, if args is a sequence, it will be converted to a string in a manner described in Converting an argument sequence to a string on Windows. This is because the underlying CreateProcess() operates on strings.

With shell=True:

On Unix with shell=True, the shell defaults to /bin/sh. If args is a string, the string specifies the command to execute through the shell. This means that the string must be formatted exactly as it would be when typed at the shell prompt. This includes, for example, quoting or backslash escaping filenames with spaces in them. If args is a sequence, the first item specifies the command string, and any additional items will be treated as additional arguments to the shell itself.

On Windows with shell=True, the COMSPEC environment variable specifies the default shell. The only time you need to specify shell=True on Windows is when the command you wish to execute is built into the shell (e.g. dir or copy). You do not need shell=True to run a batch file or console-based executable.

(all emphasis mine)

More Related Contents:

  1. Actual meaning of ‘shell=True’ in subprocess
  2. How to terminate a python subprocess launched with shell=True
  3. How to use `subprocess` command with pipes
  4. Python subprocess readlines() hangs
  5. How to redirect output with subprocess in Python?
  6. Python subprocess get children’s output to file and terminal?
  7. Subprocess changing directory
  8. Popen waiting for child process even when the immediate child has terminated
  9. Python popen command. Wait until the command is finished
  10. Understanding Popen.communicate
  11. Execute terminal command from python in new terminal window?
  12. Python: how to kill child process(es) when parent dies?
  13. OSError: [WinError 193] %1 is not a valid Win32 application
  14. subprocess.Popen() error (No such file or directory) when calling command with arguments as a string
  15. Using subprocess to run Python script on Windows
  16. running multiple bash commands with subprocess
  17. Keep a subprocess alive and keep giving it commands? Python
  18. Python output to Console within Subprocess from the child scricpt
  19. python getoutput() equivalent in subprocess [duplicate]
  20. Python Subprocess.Popen from a thread
  21. Why subprocess.Popen doesn’t work when args is sequence?
  22. How to run multiple commands synchronously from one subprocess.Popen command?
  23. Redirect subprocess stderr to stdout
  24. Interacting with bash from python
  25. Event Driven System Call in Python
  26. How do I eliminate Windows consoles from spawned processes in Python (2.7)? [duplicate]
  27. “subprocess.Popen” – checking for success and errors
  28. Run subprocess and print output to logging
  29. subprocess call ffmpeg (command line)
  30. How can I capture the stdout output of a child process?

Leave a Comment