[issue26351] Occasionally check for Ctrl-C in long-running operations like sum

[Trey Hunner]

Trey Hunner added the comment:

This is a problem I experience occasionally while teaching and while developing teaching curriculum.

I tend to close problem windows quickly enough to avoid a computer crash in front of a live audience, but it's still an annoyance to get the REPL state back to the way I had it before killing the process.

This mostly happens when I'm teaching iterators or itertools, but occasionally I hit a "Ctrl-C free zone" in other ways.  I believe this memory-filling snippet wouldn't respond to Ctrl-C either: x=[0]*2**30

I hadn't thought to report a bug on this because my use seemed niche.  I mostly get this error while demonstrating concepts via weird/incorrect code at the REPL.

----------
nosy: +trey

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26351>
_______________________________________