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 vstinner
Recipients gvanrossum, vstinner, yselivanov
Date 2015-11-12.09:55:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1447322128.43.0.475707567423.issue25606@psf.upfronthosting.co.za>
In-reply-to
Content
Not all implementations of asyncio event loops can provide the "socket" transport extra info. See for example this discussion on libuv:
https://github.com/python/asyncio/issues/286

The information should be marked as "optional", or at least we should document that it can miss depending on the event loop.

I guess that other info should be marked as optional.
History
Date User Action Args
2015-11-12 09:55:28vstinnersetrecipients: + vstinner, gvanrossum, yselivanov
2015-11-12 09:55:28vstinnersetmessageid: <1447322128.43.0.475707567423.issue25606@psf.upfronthosting.co.za>
2015-11-12 09:55:28vstinnerlinkissue25606 messages
2015-11-12 09:55:28vstinnercreate