[issue4897] PyIter_Next documentation inconsistent with implementation

Benjamin Peterson added the comment: The reason I linked to that issue is that the proposed patch brings the implementation inline with the documentation as you wished. :) ___ Python tracker

[issue4897] PyIter_Next documentation inconsistent with implementation

garcia added the comment: Thanks for the quick response. I see that the discussion in 3720 implicitly involves the implementation of PyIter_Next, but the documentation for PyIter_Next (and its conflict with the implementation) is not mentioned. ___ Python

[issue4897] PyIter_Next documentation inconsistent with implementation

Benjamin Peterson added the comment: Closing a duplicate of #3720. -- nosy: +benjamin.peterson resolution: -> duplicate status: open -> closed superseder: -> segfault in for loop with evil iterator ___ Python tracker

[issue4897] PyIter_Next documentation inconsistent with implementation

New submission from garcia : The documentation for PyIter_Next says it will raise TypeError if the object passed to it is not an iterator. However, the implementation in abstract.c performs an assert rather than raising TypeError. I would prefer if the implementation were adjusted to match t