list iterator `__setstate__()` differs for exhausted iterator GIL vs. non-GIL

Or is this too pedantic?

GIL enabled:

$ ./python
Python 3.14.0a4+ (heads/main:f3980af38b, Jan 21 2025, 11:34:12) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> it = iter([1]); list(it)
[1]
>>> it.__setstate__(0); list(it)
[]

GIL disabled:

$ ./python
Python 3.14.0a4+ experimental free-threading build (heads/main:f3980af38b, Jan 21 2025, 11:31:38) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> it = iter([1]); list(it)
[1]
>>> it.__setstate__(0); list(it)
[1]

v3.14, current main, its a one line fix.

Linked PRs

• gh-146269

首先在启用 GIL 和 free-threading 的 Python 构建中分别复现所列的迭代器行为，然后跟踪 list iterator setstate() 入口点。完成标准是：在两种构建中，已耗尽的迭代器在 setstate(0) 之后的行为都保持一致；该 issue 提到了相关的 PR gh-146269。