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.

Author vstinner
Recipients davin, pablogsal, pitrou, vstinner
Date 2019-07-08.08:20:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1562574036.34.0.167420569338.issue37507@roundup.psfhosted.org>
In-reply-to
Content
> There is no reason to expose "stop the forkserver" to users. How the forkserver process works, what tasks it handles, is an implementation detail. If users start "stopping the forkserver" in their applications for no good to reason, they might get bugs now or later that they wouldn't get otherwise.

Well, we already had this conversation before. I really dislike APIs which hold resources but disallow to "release resources", especially when a resource is not a few bytes of memory, but a whole process.

Since there is a method to start the server (ensure_running), I would like to control when it's stopped "to ensure that errors are properly reported if something goes wrong."

That's why I added Process.close() in Python 3.7 and ResourceWarning in Pool in Python 3.8.

Here I don't propose to add a ResourceWarning if the server is not stopped explicitly. I only propose to add a method if the developer wants to control when it's stopped.
History
Date User Action Args
2019-07-08 08:20:36vstinnersetrecipients: + vstinner, pitrou, davin, pablogsal
2019-07-08 08:20:36vstinnersetmessageid: <1562574036.34.0.167420569338.issue37507@roundup.psfhosted.org>
2019-07-08 08:20:36vstinnerlinkissue37507 messages
2019-07-08 08:20:35vstinnercreate