On May 10, 12:07 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> On May 10, 8:26 am, Adam Atlas <[EMAIL PROTECTED]> wrote:
>
> > I'm trying to figure out if there's any defined behaviour in PEP 333
> > for instances where an application returns an iterable as usual
> > without error, but that ite
On May 10, 8:26 am, Adam Atlas <[EMAIL PROTECTED]> wrote:
> I'm trying to figure out if there's any defined behaviour in PEP 333
> for instances where an application returns an iterable as usual
> without error, but that iterable's next() method eventually raises an
> exception. Since any data ther
I'm trying to figure out if there's any defined behaviour in PEP 333
for instances where an application returns an iterable as usual
without error, but that iterable's next() method eventually raises an
exception. Since any data theretofore returned by the iterable must be
assumed to have already b
