Message164133
| Author |
tim.golden |
| Recipients |
Devin Jeanpierre, Dude-X, amaury.forgeotdarc, brian.curtin, christian.heimes, loewis, mhammond, pitrou, r.david.murray, ronaldoussoren, santoso.wijaya, tim.golden |
| Date |
2012年06月27日.09:33:46 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1340789627.24.0.612606927872.issue1677@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Just to confirm: I can reproduce this more or less consistently on all versions of Python 2.2 -> 3.2 on Windows 7. Those are distribution builds -- ie not debug builds I've made myself. But it certainly does occur on a debug build of 2.7.
I'm trying to narrow it down through some instrumentation (read: printf) on the 2.7 branch. The MSDN page for signal warns that a separate thread will be created for the signal handler which will muddy the waters. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年06月27日 09:33:47 | tim.golden | set | recipients:
+ tim.golden, loewis, mhammond, ronaldoussoren, amaury.forgeotdarc, pitrou, christian.heimes, Dude-X, Devin Jeanpierre, r.david.murray, brian.curtin, santoso.wijaya |
| 2012年06月27日 09:33:47 | tim.golden | set | messageid: <1340789627.24.0.612606927872.issue1677@psf.upfronthosting.co.za> |
| 2012年06月27日 09:33:46 | tim.golden | link | issue1677 messages |
| 2012年06月27日 09:33:46 | tim.golden | create |
|