Issue 30244: Emit a ResourceWarning in concurrent.futures executor destructors

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/74430

classification

Title:	Emit a ResourceWarning in concurrent.futures executor destructors
Type:	resource usage	Stage:	resolved
Components:	Library (Lib)	Versions:	Python 3.7

process

Status:	closed	Resolution:	out of date
Dependencies:		Superseder:
Assigned To:		Nosy List:	vstinner, xiang.zhang
Priority:	normal	Keywords:

Created on 2017-05-03 07:18 by vstinner, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (1)
msg292849 - (view)	Author: STINNER Victor (vstinner) *	Date: 2017-05-03 07:18
Follow-up of issues: * issue #30110: test_asyncio reports reference leak, forgot to shutdown concurrent.futures.ProcessPoolExecutor() * issue #30171: Emit ResourceWarning in multiprocessing Queue destructor I propose to emit a ResourceWarning warning in concurrent.futures executor destructor if it wasn't cleaned up properly, if shutdown() wasn't called.

msg292849 - (view)

Author: STINNER Victor (vstinner) * (Python committer)

Date: 2017-05-03 07:18

Follow-up of issues:
* issue #30110: test_asyncio reports reference leak, forgot to shutdown concurrent.futures.ProcessPoolExecutor()
* issue #30171: Emit ResourceWarning in multiprocessing Queue destructor

I propose to emit a ResourceWarning warning in concurrent.futures executor destructor if it wasn't cleaned up properly, if shutdown() wasn't called.

History
Date	User	Action	Args
2022-04-11 14:58:46	admin	set	github: 74430
2018-09-19 23:11:41	vstinner	set	status: open -> closed resolution: out of date stage: resolved
2017-05-03 07:18:07	vstinner	create