Adam Olsen wrote: > What's the rationale for IOError instead of ValueError? Isn't it an > error in the application to apply the buffering layer to a > non-blocking socket, and not something related to a connection reset?
Good point -- I often put a try-except for EnvironmentError around things to catch errors resulting from external conditions and report them to the user. So I'd prefer something that didn't descend from EnvironmentError for this. TypeError might even be more appropriate than ValueError, since a non-blocking socket could be considered the wrong type of object to do buffered I/O on. -- Greg _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
