Issue 25606: asyncio doc: 'socket' transport extra info is not mandatory (original) (raw)

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/69792

classification

process

Created on 2015-11-12 09:55 by vstinner, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (5)
msg254527 - (view)	Author: STINNER Victor (vstinner) *	Date: 2015-11-12 09:55
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.
msg254541 - (view)	Author: Guido van Rossum (gvanrossum) *	Date: 2015-11-12 18:04
The word 'optional' is literally the second word of the description of get_extra_info(). WHat more do you want?
msg254554 - (view)	Author: STINNER Victor (vstinner) *	Date: 2015-11-12 20:27
Guido van Rossum added the comment: > The word 'optional' is literally the second word of the description of get_extra_info(). WHat more do you want? Hum, it can be surprising for users that an application works on "asyncio" but doesn't work on "libuv asyncio". We should explicitly explain that the availability of some information depend on the event loop.
msg254555 - (view)	Author: Guido van Rossum (gvanrossum) *	Date: 2015-11-12 20:37
Well I don't know how adding a note to the doc is going to change that much (those users probably don't read the docs but copy some example), but go ahead and add something.
msg297109 - (view)	Author: STINNER Victor (vstinner) *	Date: 2017-06-28 01:17
It seems like Guido doesn't like the idea, so I just close the issue :-)