Message321459
> 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. |
|
Date |
User |
Action |
Args |
2018-07-11 14:34:44 | vstinner | set | recipients:
+ vstinner, gvanrossum, asvetlov, yselivanov |
2018-07-11 14:34:44 | vstinner | set | messageid: <1531319684.46.0.56676864532.issue34075@psf.upfronthosting.co.za> |
2018-07-11 14:34:44 | vstinner | link | issue34075 messages |
2018-07-11 14:34:44 | vstinner | create | |
|