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 andreasvc
Recipients andreasvc, bquinlan, josh.r, mark.dickinson
Date 2014-05-07.23:15:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1399504538.12.0.586752797168.issue21423@psf.upfronthosting.co.za>
In-reply-to
Content
Here's a patch. I have added initializer and initargs keywords to both ThreadPoolExecutor and ProcessPoolExecutor, with the same semantics as multiprocessing.Pool.

I couldn't figure out what to do if the initializer fails with a ProcessPoolExecutor: how to properly send the traceback back? I also haven't gotten around to figure out how to write tests.
I haven't added unitializers, don't know if they would be useful.
History
Date User Action Args
2014-05-07 23:15:38andreasvcsetrecipients: + andreasvc, bquinlan, mark.dickinson, josh.r
2014-05-07 23:15:38andreasvcsetmessageid: <1399504538.12.0.586752797168.issue21423@psf.upfronthosting.co.za>
2014-05-07 23:15:38andreasvclinkissue21423 messages
2014-05-07 23:15:37andreasvccreate