➜

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 YAtOff
Recipients YAtOff, asvetlov, yselivanov
Date 2021-10-20.07:57:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1634716632.31.0.427704063338.issue45533@roundup.psfhosted.org>
In-reply-to
Content 
From https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.sock_connect :

Changed in version 3.5.2: address no longer needs to be resolved. sock_connect will try to check if the address is already resolved by calling socket.inet_pton(). If not, loop.getaddrinfo() will be used to resolve the address.

This used to be true in Python 3.7, but in the newer versions, no resolution is done. It could be seen in the source code - the loop implementation is changed and the new one doesn't resolve the address.

https://github.com/python/cpython/blob/085ccb0f177988065dbe9ef4c5cda434560066bc/Lib/asyncio/proactor_events.py#L703

https://github.com/python/cpython/blob/085ccb0f177988065dbe9ef4c5cda434560066bc/Lib/asyncio/windows_events.py#L576
History
Date User Action Args
2021-10-20 07:57:12YAtOffsetrecipients: + YAtOff, asvetlov, yselivanov
2021-10-20 07:57:12YAtOffsetmessageid: <1634716632.31.0.427704063338.issue45533@roundup.psfhosted.org>
2021-10-20 07:57:12YAtOfflinkissue45533 messages
2021-10-20 07:57:12YAtOffcreate