Skip to main content

Browse the archive

Staging
v0.5.1
https://github.com/python/cpython
09 December 2020, 11:06:31 UTC
Revision d9bc543cbb9681f77d94864d05e2ba2d353e6de9 authored by Gregory P. Smith on 21 February 2019, 01:35:54 UTC, committed by GitHub on 21 February 2019, 01:35:54 UTC 
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.
1 parent 9b0c681
Raw File
Tip revision: d9bc543cbb9681f77d94864d05e2ba2d353e6de9 authored by Gregory P. Smith on 21 February 2019, 01:35:54 UTC
Re-init _Py_UnhandledKeyboardInterrupt before run. (GH-11963)
Tip revision: d9bc543
CODE_OF_CONDUCT.md 
# Code of Conduct

Please note that all interactions on
[Python Software Foundation](https://www.python.org/psf-landing/)-supported
infrastructure is [covered](https://www.python.org/psf/records/board/minutes/2014-01-06/#management-of-the-psfs-web-properties>)
by the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/),
which includes all infrastructure used in the development of Python itself
(e.g. mailing lists, issue trackers, GitHub, etc.).

In general this means everyone is expected to be open, considerate, and
respectful of others no matter what their position is within the project.
back to top