Message117358
> I'm not convinced hiding operating system bugs is a good idea.
Do you propose to let the error raise then?
The point of frameworks such as asyncore and twisted is to hide all system-specific errors as much as possible and provide a portable interface across all platforms.
AFAICT, the whole point of this issue is that there should be only one way for an asyncore-based server to accept an incoming connection, possibly avoiding the user to deal with low-level details such as catching EWOULDBLOCK/ECONNABORTED/... in his application, and looking for accept() returning None is one possibility.
As I said, in a better designed framework the user shouldn't be supposed to call accept() at all, but that's how asyncore is designed. |
|
Date |
User |
Action |
Args |
2010-09-25 11:43:42 | giampaolo.rodola | set | recipients:
+ giampaolo.rodola, josiahcarlson, pitrou, matejcik, dmalcolm, santoso.wijaya, BreamoreBoy |
2010-09-25 11:43:41 | giampaolo.rodola | set | messageid: <1285415021.97.0.618894500609.issue6706@psf.upfronthosting.co.za> |
2010-09-25 11:43:40 | giampaolo.rodola | link | issue6706 messages |
2010-09-25 11:43:39 | giampaolo.rodola | create | |
|