Skip to content

[2.7] bpo-28994: Fixed errors handling in atexit._run_exitfuncs(). (GH-2034) #2123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 12, 2017

Conversation

serhiy-storchaka
Copy link
Member

The traceback no longer displayed for SystemExit raised in a callback registered by atexit..
(cherry picked from commit 3fd54d4)

…ythonGH-2034)

The traceback no longer displayed for SystemExit raised in a callback registered by atexit..
(cherry picked from commit 3fd54d4)
@serhiy-storchaka serhiy-storchaka added the type-bug An unexpected behavior, bug, or error label Jun 12, 2017
@serhiy-storchaka serhiy-storchaka merged commit 0cc43df into python:2.7 Jun 12, 2017
@serhiy-storchaka serhiy-storchaka deleted the backport-3fd54d4-2.7 branch June 12, 2017 06:10
@orivej
Copy link
Contributor

orivej commented Sep 11, 2018

This should not have been merged: there was no Modules/atexitmodule.c in Python 2.7 before this PR.

@ZackerySpytz
Copy link
Contributor

@orivej Thanks, I've reported this on the bug tracker (https://bugs.python.org/issue28994).

@serhiy-storchaka
Copy link
Member Author

Thank you for catching this @orivej!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants