[New-bugs-announce] [issue45533] loop.sock_connect doesn't resolve the address parameter on Windows

[Yavor Atov]

New submission from Yavor Atov <yavor.atov at gmail.com>:

>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

----------
components: asyncio
messages: 404398
nosy: YAtOff, asvetlov, yselivanov
priority: normal
severity: normal
status: open
title: loop.sock_connect doesn't resolve the address parameter on Windows
type: behavior
versions: Python 3.10, Python 3.11, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue45533>
_______________________________________