Skip to content
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

Avoid a badly-timed SIGINT from calling sys.exit #336

Closed
wants to merge 1 commit into from

Conversation

fdr
Copy link

@fdr fdr commented Sep 9, 2011

Inclusion of that code was probably unintentional to begin with.

Would manifest as (without overridden signal handlers): SIGINT causing
sudden termination of a Python process when unlucky.

Signed-off-by: Daniel Farina drfarina@acm.org

Inclusion of that code was probably unintentional to begin with.

Would manifest as (without overridden signal handlers): SIGINT causing
sudden termination of a Python process when unlucky.

Signed-off-by: Daniel Farina <drfarina@acm.org>
@garnaat
Copy link
Member

garnaat commented Sep 13, 2011

I agree that the sys.exit() is undesirable but it seems it could still be useful to be able to ^C out of a retry loop when in interactive mode.

@fdr
Copy link
Author

fdr commented Sep 14, 2011

Does the only other exception handling at this level -- except self.http_exceptions, e: -- catch the KeyboardError? It seems like it'd propagate and rewind the stack anyway. What is absorbing it?

@garnaat garnaat closed this in e8edf55 Sep 19, 2011
@garnaat
Copy link
Member

garnaat commented Sep 19, 2011

You are right. It is completely unnecessary. Now removed.

msabramo pushed a commit to msabramo/boto that referenced this pull request Nov 28, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants