Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.lang.python
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion KeyboardInterrupt eats my error and then won't be caught
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Philip Semanchuk  
View profile  
 More options Jun 21 2009, 10:49 am
Newsgroups: comp.lang.python
From: Philip Semanchuk <phi...@semanchuk.com>
Date: Sun, 21 Jun 2009 10:49:42 -0400
Local: Sun, Jun 21 2009 10:49 am
Subject: Re: KeyboardInterrupt eats my error and then won't be caught
Print | View thread | Show original | Report this message | Find messages by this author

On Jun 20, 2009, at 10:21 PM, greg wrote:

> Philip Semanchuk wrote:

>> Best of all, PyErr_CheckSignals() doesn't interfere with a Python-  
>> level signal handler if one is set.

> Ah, I hadn't realised that you were doing this in C
> code, and I was trying to think of a Python-level
> solution.

> For C code, the solution you give sounds like a
> good one.

> My only misgiving is that the user might expect to
> get a KeyboardInterrupt in response to Ctrl-C, so
> it might be better to just let it propagate instead
> of turning it into a different exception.

I completely agree. The simple solution (for me) is to handle all  
return codes of EINTR the same way which is to raise posix_ipc.Error  
with the message "The wait was interrupted by a signal". But that  
loses information. KeyboardInterrupt is very specific while  
posix_ipc.Error is generic and even parsing the message doesn't tell  
much more.

When my C code sees EINTR, I will probably raise KeyboardError when I  
see that and add a specific posix_ipc.SignalError to raise in other  
EINTR circumstances.

Thanks,
Philip


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google