Is anyone else interested in implementing this small feature for concurrent.futures?
On Fri, Jan 3, 2020 at 18:28 Miguel Ángel Prosper < firstname.lastname@example.org> 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 -- email@example.com To unsubscribe send an email to firstname.lastname@example.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://email@example.com/message/FGTSBG... Code of Conduct: http://python.org/psf/codeofconduct/