On Sun, Apr 2, 2017 at 4:08 PM, Terry Reedy wrote:
> Both are subclasses of OSError but mean different things. TimeoutError
> means that something in 'your system' did not respond. Socket.timeout means
> that a foreign system did not respond. (I am leaving out a local socket
> connection.) The
On 4/1/2017 3:27 PM, Ram Rachum wrote:
Today I got burned because I had code that did this:
except TimeoutError:
When it should have done this:
except socket.timeout:
Both are subclasses of OSError but mean different things. TimeoutError
means that something in 'your system' did no
On Sun, Apr 2, 2017 at 1:11 PM, Steven D'Aprano wrote:
> On the face of it, this isn't a serious problem. It seems to me rather
> like mistakenly writing:
>
> except TypeError
>
> when you actually intended to write:
>
> except ZeroDivisionError
>
> You failed to catch the exception that y
On Sat, Apr 01, 2017 at 09:27:34PM +0200, Ram Rachum wrote:
> Today I got burned because I had code that did this:
>
> except TimeoutError:
>
> When it should have done this:
>
> except socket.timeout:
On the face of it, this isn't a serious problem. It seems to me rather
like mistaken
Today I got burned because I had code that did this:
except TimeoutError:
When it should have done this:
except socket.timeout:
There's also another timeout error class in asyncio.
Initially I thought, why not make them all use the same exception class?
But Guido objects to that:
I co
