Message315761
| Author | pdgoins-work |
|---|---|
| Recipients | neologix, pdgoins-work, pitrou, tim.peters, tupl, vstinner |
| Date | 2018-04-25.22:43:47 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1524696227.87.0.682650639539.issue21822@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I've confirmed this issue on Windows. Attached is an SSCCE which seems to reliably reproduce the issue in a Windows environment. Long story short: if a KeyboardInterrupt occurs during Thread.join(), there's a good chance that Thread._is_stopped never gets set. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-04-25 22:43:47 | pdgoins-work | set | recipients: + pdgoins-work, tim.peters, pitrou, vstinner, neologix, tupl |
| 2018-04-25 22:43:47 | pdgoins-work | set | messageid: <1524696227.87.0.682650639539.issue21822@psf.upfronthosting.co.za> |
| 2018-04-25 22:43:47 | pdgoins-work | link | issue21822 messages |
| 2018-04-25 22:43:47 | pdgoins-work | create | |