Diez B. Roggisch wrote:
> Efrat Regev schrieb:
>> [EMAIL PROTECTED] wrote:
>>> On May 1, 2:23 pm, Efrat Regev <[EMAIL PROTECTED]> wrote:
>>>
So my question is if there's a way to "grab" the output as it's being
generated. It doesn't matter if the solution is blocking (as opposed to
c
Efrat Regev schrieb:
> [EMAIL PROTECTED] wrote:
>> On May 1, 2:23 pm, Efrat Regev <[EMAIL PROTECTED]> wrote:
>>
>>> So my question is if there's a way to "grab" the output as it's being
>>> generated. It doesn't matter if the solution is blocking (as opposed to
>>> callback based), since threads ca
[EMAIL PROTECTED] wrote:
> On May 1, 2:23 pm, Efrat Regev <[EMAIL PROTECTED]> wrote:
>
>> So my question is if there's a way to "grab" the output as it's being
>> generated. It doesn't matter if the solution is blocking (as opposed to
>> callback based), since threads can handle this. I just don't
On May 1, 2:23 pm, Efrat Regev <[EMAIL PROTECTED]> wrote:
> So my question is if there's a way to "grab" the output as it's being
> generated. It doesn't matter if the solution is blocking (as opposed to
> callback based), since threads can handle this. I just don't know how to
> "grab" the output
Hello,
Suppose I want to run from within a Python GUI app some long-output
shell call. For example, from within Python I might want to call
g++ foo.cpp
I already know there are many ways to do this, e.g.,
commands.getstatusoutput('g++ foo.cpp') to name one.
The problem is that thi
