➜

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 gvanrossum
Recipients asvetlov, gvanrossum, vstinner, yselivanov
Date 2018-07-11.14:53:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJKm4TgPF1upo4URx_QD8Hz+SyHU42kSpMehSTEDcTdVHQ@mail.gmail.com>
In-reply-to <[email protected]>
Content 
I disagree. Other than subclasses of thread executor, what are you going to
pass in? A mock?

On Wed, Jul 11, 2018 at 7:34 AM STINNER Victor <[email protected]>
wrote:

>
> STINNER Victor <[email protected]> added the comment:
>
> > I think we'll only allow instances of c.f.ThreadPoolExecutor (and its
> subclasses) to be passed to set_default_executor.  That's a more robust
> check than just guarding against ProcessPoolExecutor.
>
> I suggest to only reject ProcessPoolExecutor, instead of having a very
> specific test on ThreadPoolExecutor which might fail with funky but valid
> thread executor.
>
> ----------
> nosy: +vstinner
>
> _______________________________________
> Python tracker <[email protected]>
> <https://bugs.python.org/issue34075>
> _______________________________________
>
-- 
--Guido (mobile)
History
Date User Action Args
2018-07-11 14:53:02gvanrossumsetrecipients: + gvanrossum, vstinner, asvetlov, yselivanov
2018-07-11 14:53:02gvanrossumlinkissue34075 messages
2018-07-11 14:53:02gvanrossumcreate