Message 381553 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	asvetlov
Recipients	alex, asvetlov, bquinlan, christian.heimes, corona10, davin, dstufft, janssen, miss-islington, pitrou, serhiy.storchaka, vstinner, yselivanov
Date	2020-11-21.11:58:39
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1605959919.61.0.122287128517.issue42413@roundup.psfhosted.org>
In-reply-to

Content
In futures and asyncio TimeoutError has no errno. I'm not sure should we care but I consider it as a show stopper. On another hand, two distinct timeout classes confuse people. I had many conversions about this during the aiohttp support. asyncio can raise both TimeoutError and asyncio.TimeoutError which is... unexpected at least.

In futures and asyncio TimeoutError has no errno.

I'm not sure should we care but I consider it as a show stopper.

On another hand, two distinct timeout classes confuse people. I had many conversions about this during the aiohttp support.  asyncio can raise both TimeoutError and asyncio.TimeoutError which is... unexpected at least.

History
Date	User	Action	Args
2020-11-21 11:58:39	asvetlov	set	recipients: + asvetlov, bquinlan, janssen, pitrou, vstinner, christian.heimes, alex, serhiy.storchaka, yselivanov, dstufft, davin, corona10, miss-islington
2020-11-21 11:58:39	asvetlov	set	messageid: <1605959919.61.0.122287128517.issue42413@roundup.psfhosted.org>
2020-11-21 11:58:39	asvetlov	link	issue42413 messages
2020-11-21 11:58:39	asvetlov	create