Message from discussion subprocess call is not waiting.
Received: by 10.224.31.20 with SMTP id w20mr2476121qac.2.1347644294241;
Fri, 14 Sep 2012 10:38:14 -0700 (PDT)
Received: by 10.236.154.194 with SMTP id h42mr712234yhk.8.1347644294195; Fri,
14 Sep 2012 10:38:14 -0700 (PDT)
Date: Fri, 14 Sep 2012 10:38:14 -0700 (PDT)
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=220.127.116.11; posting-account=_dIAQQoAAAB7Yieol6fmkK_HviJUbJt3
References: <email@example.com> <firstname.lastname@example.org>
Subject: Re: subprocess call is not waiting.
From: Wanderer <wande...@dialup4less.com>
Injection-Date: Fri, 14 Sep 2012 17:38:14 +0000
Content-Type: text/plain; charset=ISO-8859-1
On Friday, September 14, 2012 8:22:44 AM UTC-4, pauls...@gmail.com wrote:
> os.system worked fine, and I found something in another section of code that was causing the "Too many open errors." (I was fooled, because output from subprocess call didn't seem to be coming out until the open files error.
> I'll go back and play with subprocess.call more, since os.system works. That's interesting about using shlex at run time. Is that just for the sake of computational cost?
I never got the hang of subprocess, either. I ended up wrapping os.system in a python file and using subprocess to call that with:
This works for me. I'm using Windows 7.