➜

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 yselivanov
Recipients asvetlov, gvanrossum, yselivanov
Date 2018-07-09.15:29:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1531150174.99.0.56676864532.issue34075@psf.upfronthosting.co.za>
In-reply-to
Content 
I've had a few conversations with people who were confused that asyncio starts to behave weirdly when a ProcessPoolExecutor is set as the default one.  We don't really test that asyncio's built-in functionality (like DNS resolving) works well with a process-pool, which leads to bug reports like [1].  Third-party libraries also always assume that the loop is always configured to use the ThreadPoolExecutor (as it is by default), and also don't even test against ProcessPool.

My idea here would be to deprecate setting ProcessPoolExecutor as a default one in 3.8 and prohibit that in 3.9.

Guido, Andrew, what do you think?

[1] https://bugs.python.org/issue34073
History
Date User Action Args
2018-07-09 15:29:35yselivanovsetrecipients: + yselivanov, gvanrossum, asvetlov
2018-07-09 15:29:34yselivanovsetmessageid: <1531150174.99.0.56676864532.issue34075@psf.upfronthosting.co.za>
2018-07-09 15:29:34yselivanovlinkissue34075 messages
2018-07-09 15:29:34yselivanovcreate