Message350134
| Author |
gregory.p.smith |
| Recipients |
Mark.Shannon, deleted0524, erik.bray, gregory.p.smith, jdemeyer, ncoghlan, njs, rhettinger, serhiy.storchaka, xgdomingo, yselivanov |
| Date |
2019年08月21日.23:32:08 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1566430328.67.0.593457758293.issue29988@roundup.psfhosted.org> |
| In-reply-to |
| Content |
The signal handler in this case is CPython's internal signal handling system thus any such onus falls on us...
The great signal handling hack of "set a flag that the interpreter loop checks on occasion" trick lasted a long time, but our VM has since evolved to be much more complicated than every bytecode being a safe interrupt point.
FYI - Most of the in-room conversation we tried to capture on this issue thread was at the core dev sprint a couple years ago (Sept 2017). It'll similarly take me a while to swap this context back in. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2019年08月21日 23:32:08 | gregory.p.smith | set | recipients:
+ gregory.p.smith, rhettinger, ncoghlan, njs, Mark.Shannon, erik.bray, serhiy.storchaka, jdemeyer, yselivanov, deleted0524, xgdomingo |
| 2019年08月21日 23:32:08 | gregory.p.smith | set | messageid: <1566430328.67.0.593457758293.issue29988@roundup.psfhosted.org> |
| 2019年08月21日 23:32:08 | gregory.p.smith | link | issue29988 messages |
| 2019年08月21日 23:32:08 | gregory.p.smith | create |
|