[issue32576] concurrent.futures.thread potential deadlock due to Queue in weakref callback

2018-01-17 Thread Mark Dickinson
Mark Dickinson added the comment: See also https://bugs.python.org/issue21009 -- nosy: +mark.dickinson ___ Python tracker ___

[issue32576] concurrent.futures.thread potential deadlock due to Queue in weakref callback

2018-01-17 Thread Antoine Pitrou
Change by Antoine Pitrou : -- keywords: +patch pull_requests: +5069 stage: needs patch -> patch review ___ Python tracker ___

[issue32576] concurrent.futures.thread potential deadlock due to Queue in weakref callback

2018-01-17 Thread Antoine Pitrou
Antoine Pitrou added the comment: We could also switch multiprocessing.Pool. Unfortunately some code in multiprocessing.Pool relies on internal details of queue.Queue (!). -- ___ Python tracker

[issue32576] concurrent.futures.thread potential deadlock due to Queue in weakref callback

2018-01-16 Thread Gregory P. Smith
New submission from Gregory P. Smith : As a follow up to https://bugs.python.org/issue14976 which just introduced queue.SimpleQueue: concurrent.futures.thread currently uses a queue.Queue() from weakref callbacks which could in theory lead to a deadlock when periodic gc