Antoine Pitrou solipsis at pitrou.net
Sun Dec 15 00:19:05 CET 2013

• Previous message: [Python-Dev] Default SIGINT handling dangerous?
• Next message: [Python-Dev] Default SIGINT handling dangerous?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Sat, 14 Dec 2013 15:14:10 +0100
Jurko Gospodnetić <jurko.gospodnetic at pke.hr> wrote:
> 
>    I believe the current Python default SIGINT handling by raising an 
> asynchronous KeyboardInterrupt exception is dangerous, and can directly 
> cause Python interpreter crashes even if no user code is involved, or 
> any sort of other 'undefined behaviour' if it is.

It would be nice if you could get an actual C traceback, and open an
issue on the bug tracker. Python isn't supposed to crash willy-nilly
when Ctrl+C is pressed.

(also, which Python version is this?)

Regards

Antoine.

---

• Previous message: [Python-Dev] Default SIGINT handling dangerous?
• Next message: [Python-Dev] Default SIGINT handling dangerous?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list