➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zby1234
Recipients paul.moore, steve.dower, tim.golden, zach.ware, zby1234
Date 2021-03-05.16:16:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1614960967.41.0.0636989902685.issue43409@roundup.psfhosted.org>
In-reply-to
Content 
Please run joinbug.py and press Ctrl-C twice.

============= The output  =============

1st join
PLEASE PRESS CTRL-C TWICE, IGNORE THE 'Press any key to continue'
Press any key to continue . . . Press any key to continue . . .

thread exit
Traceback (most recent call last):
  File "D:\xxx\joinbug.py", line 21, in <module>
    t.join() # subprocess.Popen() makes join() can be interrupted
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python39\lib\threading.py", line 1033, in join
    self._wait_for_tstate_lock()
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python39\lib\threading.py", line 1049, in _wait_for_tstate_lock
    elif lock.acquire(block, timeout):
KeyboardInterrupt
2nd join
(stuck here)


============= Expected behaviour =============
either join uninterruptible
or the 2nd join doesn't deadlock.
History
Date User Action Args
2021-03-05 16:16:07zby1234setrecipients: + zby1234, paul.moore, tim.golden, zach.ware, steve.dower
2021-03-05 16:16:07zby1234setmessageid: <1614960967.41.0.0636989902685.issue43409@roundup.psfhosted.org>
2021-03-05 16:16:07zby1234linkissue43409 messages
2021-03-05 16:16:07zby1234create