Skip to content

Conversation

@vstinner
Copy link
Member

@vstinner vstinner commented Sep 4, 2017

  • bpo-31326: ProcessPoolExecutor waits for the call queue thread

concurrent.futures.ProcessPoolExecutor.shutdown() now explicitly
closes the call queue. Moreover, shutdown(wait=True) now also join
the call queue thread, to prevent leaking a dangling thread.

  • Fix for shutdown() being called twice.

(cherry picked from commit b713adf)

https://bugs.python.org/issue31326

* bpo-31326: ProcessPoolExecutor waits for the call queue thread

concurrent.futures.ProcessPoolExecutor.shutdown() now explicitly
closes the call queue. Moreover, shutdown(wait=True) now also join
the call queue thread, to prevent leaking a dangling thread.

* Fix for shutdown() being called twice.

(cherry picked from commit b713adf)
@vstinner
Copy link
Member Author

vstinner commented Sep 4, 2017

@pitrou, @applio: Is there a risk of breaking applications with this change? Is it worth it?

@pitrou
Copy link
Member

pitrou commented Sep 5, 2017

I don't terribly like this being backported. It does not fix any user-visible problem AFAIK.

@vstinner
Copy link
Member Author

vstinner commented Sep 5, 2017

I don't terribly like this being backported. It does not fix any user-visible problem AFAIK.

Ok, fine. I abandon this change.

@vstinner vstinner closed this Sep 5, 2017
@vstinner vstinner deleted the futures_join_thread36 branch September 5, 2017 16:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants