Message261513
| Author |
tjguk |
| Recipients |
jecanne, paul.moore, steve.dower, tim.golden, tjguk, vstinner, zach.ware |
| Date |
2016年03月10日.17:12:31 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<56E1AAF9.7000802@timgolden.me.uk> |
| In-reply-to |
<1457629247.39.0.490463861808.issue26531@psf.upfronthosting.co.za> |
| Content |
If I run your code, it does what I expect: pressing Ctrl-C produces
"Interrupt", doesn't print the data returned from raw_input, and doesn't
produce a stacktrace.
I'm not on Win10 and it's entirely possible that this area of the MS CRT
has been reworked: it's a bit quirky and our use of it is fairly fragile.
I'm still not clear, though, whether we have a bug or whether it's just
that your expectation is at odds with the way in which this is intended
to work.
If you think there's a bug here, could you run the code you posted in a
console window, do what actions are needed to make it fail, and then
cut-and-paste the result here, possibly as an attached file. (Don't post
a screenshot; just use the cmd window's mark-and-copy functionality to
select the visible text). |
|