coroutine is done: use the first line number of the code object instead of the
current line number of the generator frame.

The name of the coroutine is not enough because many coroutines may have the
same name. It's a common case in asyncio tests for example.

done: use the first line number of the code object instead of the current line
number of the generator frame.

The name of the coroutine is not enough because many coroutines may have the
same name. It's a common case in asyncio tests for example.

Windows was seeing the 'GET' generated by these tests as invalid and forcibly
closing the socket, causing the test to fail.

Patch by Jeff Allen.

(Based on a patch from Renee Chu.)

Closes #21801.

Closes #21801.

get_event_loop() raises an exception if there is no current loop

raises an exception if there is no current loop

Patch from Yayoi Ukai.

From the combined efforts of Berber Peksage, Andrew Svetlov, and Yayoi Ukai.

exception if the event loop is running. You must first stop the event loop and
then wait until it stopped, before closing it.

event loop is running. You must first stop the event loop and then wait until
it stopped, before closing it.

PYTHONASYNCIODEBUG env var enables debug mode of the event loop.

enables debug mode of the event loop.

PYTHONASYNCIODEBUG environment variable is set

environment variable is set

raises an exception if the current loop is not None.

Guido van Rossum wrote:

"The behavior that you can set the loop to None (and keep track of it
explicitly) is part of the spec, and this should still be supported even in
debug mode. The behavior that we raise an error if you are caught having
multiple active loops per thread is just a debugging heuristic, and it
shouldn't break code that follows the spec."

exception if the current loop is not None.

Guido van Rossum wrote:

"The behavior that you can set the loop to None (and keep track of it
explicitly) is part of the spec, and this should still be supported even in
debug mode. The behavior that we raise an error if you are caught having
multiple active loops per thread is just a debugging heuristic, and it
shouldn't break code that follows the spec."

Patch by Nikolaus Rath.

Patch by Olive Kilburn.