[issue25606] asyncio doc: 'socket' transport extra info is not mandatory

STINNER Victor added the comment: It seems like Guido doesn't like the idea, so I just close the issue :-) -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker _

[issue25606] asyncio doc: 'socket' transport extra info is not mandatory

Guido van Rossum added the comment: 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. -- ___ Python tracker

[issue25606] asyncio doc: 'socket' transport extra info is not mandatory

STINNER Victor added the comment: 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

[issue25606] asyncio doc: 'socket' transport extra info is not mandatory

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? -- ___ Python tracker ___ ___

[issue25606] asyncio doc: 'socket' transport extra info is not mandatory

New submission from STINNER Victor: 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