On 8/5/2010 7:16 PM, Joshua Russo wrote: > On Aug 4, 6:49 pm, Hassan <hsn.zam...@gmail.com> 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 waits for the process to end to output > anything. Unless I was doing something wrong, but I think I was doing > just what you describe here. > Well, readlines() inherently has to see the end of the data stream before it can return a list of all the lines that the data stream contains, so that's hardly surprising is it?
Try using readline() in a loop and see if that gives you better results. I don't guarantee it will, but at least you will have some chance if subprocess.open() *isn't* buffering the whole stream. regards Steve -- I'm no expert. "ex" == "has-been"; "spurt" == "drip under pressure" "expert" == "has-been drip under pressure". -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
