tree a24965055c43fe8a9fa152d30b07452e5c986820
parent 9b0c681e2d7e708a07e34d9c08e4424bdd4f5ebc
author Gregory P. Smith <greg@krypto.org> 1550712954 -0800
committer GitHub <noreply@github.com> 1550712954 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJcbgB6CRBK7hj4Ov3rIwAAdHIIABEMQpR4hIr+nKJkd9d5Pbal
 /7cE02+aND6EbhGoaJnoUCf3kjq7bLaEsLkYIfcaXItGHumGdak8z/AgboxlJoxe
 F5Vr0llQ+IlFPXqsFdIvQlYypTJYm9MkIQEn3Kl5tAPS0/vFosTNEnyBMnuDF3Dh
 y9a+0ZkP2KVZEbt64DCx4UXUJihCK3udyVxIGj/RYnjMDKzUBftrLhdNfZH7n42N
 wfqL1QM9pSjjv91dfFrvJttEkn8aa6ACdgXiQ4apLrNQo/1gH0ZIzy61O8/BavVq
 bijGICgDE4mCbydqBPkQ51JnqRaKpkKfVH5ORN7gj51YgkmcyvKdrSq3Glr2WHw=
 =kQv4
 -----END PGP SIGNATURE-----
 

Re-init _Py_UnhandledKeyboardInterrupt before run. (GH-11963)

Explicitly reinitialize this every eval *just in case* someone is
calling into an embedded Python where they don't care about an uncaught
KeyboardInterrupt exception (why didn't they leave
`config.install_signal_handlers` set to `0`?!?) but then later call
`Py_Main()` itself (which *checks* this flag and dies with a signal after
its interpreter exits).  We don't want a previous embedded interpreter's
uncaught exception to trigger an unexplained signal exit from a future
`Py_Main()` based one.