[issue34075] We should prohibit setting a ProcessPoolExecutor in with set_default_executor

Guido van Rossum added the comment: Of course, that's what I meant. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue34075] We should prohibit setting a ProcessPoolExecutor in with set_default_executor

Yury Selivanov added the comment: > We should warn against this in the docs right away (and backport the warning > to all previous versions that have set_executor). I think we'll only allow instances of c.f.ThreadPoolExecutor (and its subclasses) to be passed to set_default_executor.

[issue34075] We should prohibit setting a ProcessPoolExecutor in with set_default_executor

Yury Selivanov added the comment: Great! Thanks for the quick reply, Guido. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue34075] We should prohibit setting a ProcessPoolExecutor in with set_default_executor

Guido van Rossum added the comment: Yeah, that's a good idea. It was never meant for a ProcessPoolExecutor. We should warn against this in the docs right away (and backport the warning to all previous versions that have set_executor). I also support non-silent deprecation in 3.8.

[issue34075] We should prohibit setting a ProcessPoolExecutor in with set_default_executor

New submission from Yury Selivanov : 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