On Fri, 2010-08-06 at 18:35 -0100, Joshua Russo wrote:
>
>
> Nope, still no dice. Below is what I did. I modified the worker()
> function from one of the Stackoverflow examples. Let me know if I'm
> using flush properly. Keep in mind that everything you see here is
> already running in a separat
On Fri, Aug 6, 2010 at 12:17 PM, Joshua Russo wrote:
> On Aug 6, 9:57 am, "J. Cliff Dyer" wrote:
> > "Joshua Russo" wrote:
> > >On Thu, Aug 5, 2010 at 10:53 PM, Steve Holden
> wrote:
> >
> > >> On 8/5/2010 7:16 PM, Joshua Russo wrote:
> > >> > On Aug 4, 6:49 pm, Hassan wrote:
> > >> >>> Ok, so
On Aug 6, 9:57 am, "J. Cliff Dyer" wrote:
> "Joshua Russo" wrote:
> >On Thu, Aug 5, 2010 at 10:53 PM, Steve Holden wrote:
>
> >> On 8/5/2010 7:16 PM, Joshua Russo wrote:
> >> > On Aug 4, 6:49 pm, Hassan wrote:
> >> >>> Ok, so it appears that (in Python 2.5 at least) there is no way to
> >> capt
"Joshua Russo" wrote:
>On Thu, Aug 5, 2010 at 10:53 PM, Steve Holden wrote:
>
>> On 8/5/2010 7:16 PM, Joshua Russo wrote:
>> > On Aug 4, 6:49 pm, Hassan wrote:
>> >>> Ok, so it appears that (in Python 2.5 at least) there is no way to
>> capture
>> >>> the stdout of subprocess.Popen()
>> >>
>>
On Thu, Aug 5, 2010 at 10:53 PM, Steve Holden wrote:
> On 8/5/2010 7:16 PM, Joshua Russo wrote:
> > On Aug 4, 6:49 pm, Hassan wrote:
> >>> Ok, so it appears that (in Python 2.5 at least) there is no way to
> capture
> >>> the stdout of subprocess.Popen()
> >>
> >> just do this
> >>
> >> from sub
On 8/5/2010 7:16 PM, Joshua Russo wrote:
> On Aug 4, 6:49 pm, Hassan wrote:
>>> Ok, so it appears that (in Python 2.5 at least) there is no way to capture
>>> the stdout of subprocess.Popen()
>>
>> just do this
>>
>> from subprocess import Popen, PIPE
>> p = Popen([cmd], stdout=PIPE)
>> p.stdout.r
On Aug 4, 6:49 pm, Hassan wrote:
> > Ok, so it appears that (in Python 2.5 at least) there is no way to capture
> > the stdout of subprocess.Popen()
>
> just do this
>
> from subprocess import Popen, PIPE
> p = Popen([cmd], stdout=PIPE)
> p.stdout.readlines()
>
> thats it!
The problem is that it
> Ok, so it appears that (in Python 2.5 at least) there is no way to capture
> the stdout of subprocess.Popen()
just do this
from subprocess import Popen, PIPE
p = Popen([cmd], stdout=PIPE)
p.stdout.readlines()
thats it!
--
You received this message because you are subscribed to the Google Gr
On Mon, Aug 2, 2010 at 6:41 PM, Joshua Russo wrote:
> I'm creating a wxPython application that the client can run to make
> sure the installation stack is functioning properly. I want to include
> the unit test processing in this application but I've run into some
> difficulties. An additional wr
I'm creating a wxPython application that the client can run to make
sure the installation stack is functioning properly. I want to include
the unit test processing in this application but I've run into some
difficulties. An additional wrinkle I threw in was that I am using
py2exe so they don't also
10 matches
Mail list logo
