>> > I just noticed in the development docs that when a timeout on a
>> > socket occurs, socket.error is raised. I rather liked the idea
>> > that a different exception was raised for timeouts (I used Tim
>> > O'Malley's timeout_socket module).
Guido> I'd like to understand the use case better. Why would you want
Guido> to make this distinction?
In my application that uses Tim O'Malley's timeout_socket module, I do very
little different in the two cases other than to generate a different message
for the user.
As I mentioned in the subject, it is a minor quibble. If it's a pain to
modify the code to raise a distinct error, I wouldn't bother.
Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4