> Is anyone else interested in implementing this small feature for concurrent.futures?I would certainly be willing to look into it. We've been discussing the possibility of a native threadpool for asyncio in the future (https://bugs.python.org/issue32309), so it would certainly be beneficial for me to build some experience in working with the internals of the executors. I think implementing this small feature would be a good introduction.On Wed, Jan 15, 2020 at 5:37 PM Guido van Rossum <guido@python.org> wrote:(Belatedly)Is anyone else interested in implementing this small feature for concurrent.futures?--On Fri, Jan 3, 2020 at 18:28 Miguel Ángel Prosper <miguelangel.prosper@gmail.com> wrote:> It looks like you have a good handle on the code -- do you want to submit a PR to GitHub to add such a parameter?
Thanks, but I'm not really sure how to implement it in the ProcessPoolExecutor, I just think the solution is probably related to the code responsible of handling a failed initializer (since they do very similar things). On the ThreadPoolExecutor maybe I could, but I haven't really checked for side effects or weird things.
_______________________________________________
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-leave@python.org
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/FGTSBGTXW63SSXFQBASLCTXAT4M6RGGN/
Code of Conduct: http://python.org/psf/codeofconduct/
--Guido (mobile)_______________________________________________
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-leave@python.org
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/WSE2KMKFMPG2RYSJSGMRZPDJLM7DZKSG/
Code of Conduct: http://python.org/psf/codeofconduct/