[issue34173] [3.7] deadlock in /usr/lib/python3.7/concurrent/futures/thread.py

Karthikeyan Singaravelan added the comment: Thanks for the info. I am closing it as third party. -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker _

[issue34173] [3.7] deadlock in /usr/lib/python3.7/concurrent/futures/thread.py

Corey Bryant added the comment: I think we can close this issue. It was narrowed down to eventlet. Please see: https://github.com/eventlet/eventlet/issues/508 On Tue, Jul 24, 2018 at 1:54 PM Karthikeyan Singaravelan < rep...@bugs.python.org> wrote: > > Karthikeyan Singaravelan added the comm

[issue34173] [3.7] deadlock in /usr/lib/python3.7/concurrent/futures/thread.py

Karthikeyan Singaravelan added the comment: Sorry for the noise about the title change. It seems you have edited it while I was typing my comment. There was a form error while I tried submit but I ignored it to try again and it had set my title. I have reverted back to your edit. Thanks --

[issue34173] [3.7] deadlock in /usr/lib/python3.7/concurrent/futures/thread.py

Change by Corey Bryant : -- title: [3.7] possible race condition in /usr/lib/python3.7/concurrent/futures/thread.py -> [3.7] deadlock in /usr/lib/python3.7/concurrent/futures/thread.py ___ Python tracker __