Armin Rigo <[EMAIL PROTECTED]> wrote:
>
> Hi Josiah,
>
> On Fri, Jun 30, 2006 at 01:27:24PM -0700, Josiah Carlson wrote:
> > I'll just have to gracefully degrade functionality for older Pythons.
>
> More precisely, the bug shows up because in
>
> while 1:
> pass
>
> the current line
Hi Josiah,
On Fri, Jun 30, 2006 at 01:27:24PM -0700, Josiah Carlson wrote:
> I'll just have to gracefully degrade functionality for older Pythons.
More precisely, the bug shows up because in
while 1:
pass
the current line remains on the 'pass' forever. It works for a loop
like that:
"Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>
> Josiah Carlson wrote:
> > Any pointers as to why there is a difference would be appreciated.
>
> This was fixed in r35540, r35541, r35542, r35543, by Nick Bastin
> and Armin Rigo, in response to #765624. Enough pointers :-?
Yes, thank you Martin
Josiah Carlson wrote:
> Any pointers as to why there is a difference would be appreciated.
This was fixed in r35540, r35541, r35542, r35543, by Nick Bastin
and Armin Rigo, in response to #765624. Enough pointers :-?
Regards,
Martin
___
Python-Dev maili
I've previously asked on python-list, but have recieved no responses or
explanations. Maybe someone here with a better memory can help, and I
apologize for asking a somewhat off-topic question about such an archaic
version of Python.
According to my reading of Python 2.3 docs, the call to goo()
