Message 66008 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	belopolsky
Recipients	belopolsky, georg.brandl, gvanrossum, rhettinger
Date	2008-04-30.16:54:01
SpamBayes Score	0.01275837
Marked as misclassified	No
Message-id	<d38f5330804300953u59caf647gd9e564e112d9681d@mail.gmail.com>
In-reply-to	<1209573662.22.0.896193915336.issue2719@psf.upfronthosting.co.za>

Content
On Wed, Apr 30, 2008 at 12:41 PM, Guido van Rossum <report@bugs.python.org> wrote: > > Guido van Rossum <guido@python.org> added the comment: > > > .. builtin_next() should return > > NULL without an exception set and thus trigger a SystemError. > > Wrong; the iternext slot is designed to return NULL without setting an > exception. See e.g. listiter_next(). I did not know that. Thanks for the explanation. In this case, wouldn't it be cleaner to call PyIter_Next which is documented to return NULL with no exception?

On Wed, Apr 30, 2008 at 12:41 PM, Guido van Rossum
<report@bugs.python.org> wrote:
>
>  Guido van Rossum <guido@python.org> added the comment:
>
>  > ..  builtin_next() should return
>  > NULL without an exception set and thus trigger a SystemError.
>
>  Wrong; the iternext slot is designed to return NULL without setting an
>  exception.  See e.g. listiter_next().

I did not know that.  Thanks for the explanation.  In this case,
wouldn't it be cleaner to call PyIter_Next which is documented to
return NULL with no exception?

History
Date	User	Action	Args
2008-04-30 16:54:03	belopolsky	set	spambayes_score: 0.0127584 -> 0.01275837 recipients: + belopolsky, gvanrossum, georg.brandl, rhettinger
2008-04-30 16:54:02	belopolsky	link	issue2719 messages
2008-04-30 16:54:01	belopolsky	create