Python 3.12 inspecting a coroutine using `getcoroutinestate` returns the wrong state.

[gottadiveintopython]

Bug report

Bug description:

Prior to Python 3.12, we can close a just created coroutine, thus, the following test passes:

from inspect import getcoroutinestate, CORO_CLOSED


async def do_nothing():
    pass


def test_immediate_close():
    coro = do_nothing()
    coro.close()
    assert getcoroutinestate(coro) == CORO_CLOSED

But in Python 3.12, the assertion fails and getcoroutinestate(coro) still is CORO_CREATED after the coro.close(). You can confirm it from https://github.com/gottadiveintopython/py312/actions/runs/6571303025/job/17850194150.

I don't know if this is an intensional change or not, but I just wanted to tell you.

CPython versions tested on:

3.12

Operating systems tested on:

Linux

Linked PRs

• gh-111058: Change coro.cr_frame/gen.gi_frame to be None for a closed coroutine/generator. #112428
• [3.12] gh-111058: Change coro.cr_frame/gen.gi_frame to be None for a closed coroutine/generator. (GH-112428) #112589

[terryjreedy]

Same change on Windows. 3.13 like 3.12.

[Eclips4]

Bisected to f02fa64
cc @markshannon

[markshannon]

The coroutine is closed, as coro.send(None) fails. It is just that getcoroutinestate returns the wrong value.
I've updated the title accordingly.

[iritkatriel]

getcoroutinestate does this:

    if coroutine.cr_running:
        return CORO_RUNNING
    if coroutine.cr_suspended:
        return CORO_SUSPENDED
    if coroutine.cr_frame is None:
        return CORO_CLOSED
    return CORO_CREATED

coroutine.cr_frame returns None for frames which have state FRAME_CLEARED, but not for FRAME_COMPLETED.