Regarding the sample code in: http://docs.python.org/library/itertools#itertools.izip_longest

If an IndexError is raised inside an iterator in the "equivalent" code
from the docs, the generator stops and the error is swallowed.

If an IndexError is raised inside an iterator in the
"izip_longest_next" code in CPython's "Modules/itertoolsmodule.c", the
generator stops and the error propagates.

---

Reported by Adam Forsyth on the docs mailing list. More details in this SO discussion: http://stackoverflow.com/questions/7392902/izip-longest-in-itertools-how-does-rasing-indexerror-inside-the-iterator-work

I had forwarded this to Raymond, and he replied:

The itertools module code is correct.
The "equivalent" is only approximately correct 
I don't consider it to be a bug -- it is an implementation detail in an illustration.

What about at least documenting it? Since a real user ran into this and reported it as a problem, I think it would make sense to make the discrepancy explicit.

Alternatively a generalized note can be added to the documentation of itertools stating that the "equivalent" code samples are only approximate and differ in small details from the real implementations.

Well, this is for Raymond to decide.

This is marked as "wont fix" but has been fixed, the resolution should be changed.

Yep, it appears that Raymond has fixed this in changeset b0065b9087ef