I've been trying to pass a command that works in shell that only works with literal double quotes in the commandline around the "concat:file1|file2"
argument for ffmpeg.
I cant however make this work from python with subprocess.Popen()
. Anyone have an idea how one passes quotes into subprocess.Popen?
Here is the code:
command = "ffmpeg -i "concat:1.ts|2.ts" -vcodec copy -acodec copy temp.mp4"
output,error = subprocess.Popen(command, universal_newlines=True,
stdout=subprocess.PIPE,
stderr=subprocess.PIPE).communicate()
When I do this, ffmpeg won't take it any other way other than quotes around the concat segement. Is there a way to successfully pass this line to subprocess.Popen command?
Also struggling with a string argument containing spaces and not wanting to use the shell=True.
The solution was to use double quotes for the inside strings.
I'd suggest using the list form of invocation rather than the quoted string version:
This more accurately represents the exact set of parameters that are going to be passed to the end process and eliminates the need to mess around with shell quoting.
That said, if you absolutely want to use the plain string version, just use different quotes (and
shell=True
):This works with python 2.7.3 The command to pipe stderr to stdout has changed since older versions of python:
Put this in a file called test.py:
Invoke it:
It prints my hostname, which is apollo:
Read up on the manual for subprocess: http://docs.python.org/2/library/subprocess.html
Either use single quotes
'around the "whole pattern"'
to automatically escape the doubles or explicitly"escape the \"double quotes\""
. Your problem has nothing to do withPopen
as such.Just for the record, I had a problem particularly with a
list
-based command passed toPopen
that would not preserve proper double quotes around a glob pattern (i.e. what was suggested in the accepted answer) under Windows. Joining the list into a string with' '.join(cmd)
before passing it toPopen
solved the problem.I have been working with a similar issue, with running a relatively complex command over ssh. It also had multipel double quotes and single quotes. Because I was piping the command through
python
,ssh
,powershell
etc.If you can instead just convert the command into a shell script, and run the shell script through
subprocess.call/Popen/run
, these issues will go away.So depending on whether you are on windows or on linux or mac, put the following in a shell script either (
script.sh
orscript.bat
)Then you can run
Without having to worry about single quotes etc