[issue23243] asyncio: emit ResourceWarning warnings if transports/event loops are not explicitly closed

STINNER Victor added the comment: Ok, I commited my change adding destructors on Python 3.4 and newer to emit warnings when event loops or transports are not explicitly closed. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue23243] asyncio: emit ResourceWarning warnings if transports/event loops are not explicitly closed

Roundup Robot added the comment: New changeset 543f770f62f0 by Victor Stinner in branch '3.4': Issue #23243, asyncio: Emit a ResourceWarning when an event loop or a transport https://hg.python.org/cpython/rev/543f770f62f0 -- ___ Python tracker

[issue23243] asyncio: emit ResourceWarning warnings if transports/event loops are not explicitly closed

STINNER Victor added the comment: > - SelectorEventLoop._accept_connection() doesn't care of the creation of the > transport failed Fixing this issue requires to change the design of asyncio, so I chose to open a new issue: issue #2. -- ___ Pyt

[issue23243] asyncio: emit ResourceWarning warnings if transports/event loops are not explicitly closed

STINNER Victor added the comment: > Some ResourceWarning are still emited on SSL server tests. Attached server_close.patch is a work-in-process patch to fix this issue on Linux. If I understood correctly, there are two issues: - SelectorEventLoop._accept_connection() doesn't care of the creat

[issue23243] asyncio: emit ResourceWarning warnings if transports/event loops are not explicitly closed

STINNER Victor added the comment: I fixed a lot of methods and tests to ensure that all event loops and transports are properly closed. These changes were required to prepare the integration of this change. Many changed were real bug fixes: closing explicitly tranports on error avoids to leak

[issue23243] asyncio: emit ResourceWarning warnings if transports/event loops are not explicitly closed

Roundup Robot added the comment: New changeset 2f13d53f4680 by Victor Stinner in branch '3.4': Issue #23243: Fix asyncio._UnixWritePipeTransport.close() https://hg.python.org/cpython/rev/2f13d53f4680 New changeset aef0f9b4e729 by Victor Stinner in branch '3.4': Issue #23243: Close explicitly eve

[issue23243] asyncio: emit ResourceWarning warnings if transports/event loops are not explicitly closed

New submission from STINNER Victor: I propose to add destructors to transports and event loops which emit a ResourceWarning if they are not closed. The change should help to detect resource leaks and bugs. Attached patch implements this issue. It only adds destructors on Python 3.4 and later,