GeezerVison

When you're done making the requested changes, leave the comment: I have made the requested changes; please review again.

I have made the requested changes; please review again.

Thanks for making the requested changes!

@markshannon: please review the changes made to this pull request.

Thanks @iritkatriel for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13.
🐍🍒⛏🤖

Sorry, @iritkatriel, I could not cleanly backport this to 3.13 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker ec89620e5e147ba028a46dd695ef073a72000b84 3.13

Sorry, @iritkatriel, I could not cleanly backport this to 3.12 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker ec89620e5e147ba028a46dd695ef073a72000b84 3.12

GH-123209 is a backport of this pull request to the 3.13 branch.

GH-123210 is a backport of this pull request to the 3.12 branch.

@iritkatriel might it be that this fix changed the source range for exceptions in __init__ and __next__ but not for exceptions in __iter__.

class Foo:
    def __iter__(self):
        assert False

a = [x for x in Foo()]

output (Python 3.13.0rc1+):

Traceback (most recent call last):
  File "/home/frank/projects/cpython/codi.py", line 5, in <module>
    a = [x for x in Foo()]
        ^^^^^^^^^^^^^^^^^^
  File "/home/frank/projects/cpython/codi.py", line 3, in __iter__
    assert False
           ^^^^^
AssertionError

This is the example from the issue and I'm a little confused as to whether it was just forgotten or if I'm missing something here.

This is the example from the issue and I'm a little confused as to whether it was just forgotten or if I'm missing something here.

So it seems. The test doesn't check for this too. Thanks for reporting, I'll fix.