Hi, Gabriel. I missed this message initially; I apologize for not
responding sooner.
On Thu, 28 Feb 2008 18:53:28 -0500, Gabriel Genellina
<[EMAIL PROTECTED]> wrote:
>> I can reproduce the issue in the console. I'm not convinced it's
>> actually
>> a bug, unless for some reason the interp
On Thu, 28 Feb 2008 15:04:38 -0500, Ethan Metsger <[EMAIL PROTECTED]>
wrote:
>
> I can reproduce the issue in the console. I'm not convinced it's
> actually
> a bug, unless for some reason the interpreter is preventing a buffer
> flush.
Quick question.
Having eliminated some of the other
En Thu, 28 Feb 2008 18:04:38 -0200, Ethan Metsger <[EMAIL PROTECTED]>
escribió:
> On Thu, 28 Feb 2008 14:48:55 -0500, <[EMAIL PROTECTED]> wrote:
>
>> Can you reproduce the bug on the console? Or, try starting with a new
>> line in the output. Or, try a input().
>
> I can reproduce the issue in
On Thu, 28 Feb 2008 14:48:55 -0500, <[EMAIL PROTECTED]> wrote:
> Can you reproduce the bug on the console? Or, try starting with a new
> line in the output. Or, try a input().
I can reproduce the issue in the console. I'm not convinced it's actually
a bug, unless for some reason the interpre
On Feb 28, 11:49 am, "Ethan Metsger" <[EMAIL PROTECTED]> wrote:
> Hi, all.
>
> I apologize for what is perhaps a newb question. I'm in the process of
> transitioning our testing framework from Perl to Python. While that alone
> probably sets off some red flags, I'm afraid it's what I'm stuck