Allow IPv6 datagram protocol addresses

stdlib/@tests/test_cases/asyncio/check_datagram_protocol.py

@@ -0,0 +1,11 @@
+from __future__ import annotations
+
+import asyncio
+
+
+class IPv4DatagramProtocol(asyncio.DatagramProtocol):
+    def datagram_received(self, data: bytes, addr: tuple[str, int]) -> None: ...
+
+
+class IPv6DatagramProtocol(asyncio.DatagramProtocol):
+    def datagram_received(self, data: bytes, addr: tuple[str, int, int, int]) -> None: ...

stdlib/asyncio/protocols.pyi

@@ -1,6 +1,6 @@
 from _typeshed import ReadableBuffer
 from asyncio import transports
-from typing import Any
+from socket import _RetAddress
 
 # Keep asyncio.__all__ updated with any changes to __all__ here
 __all__ = ("BaseProtocol", "Protocol", "DatagramProtocol", "SubprocessProtocol", "BufferedProtocol")
@@ -27,11 +27,10 @@ class BufferedProtocol(BaseProtocol):
 class DatagramProtocol(BaseProtocol):
     __slots__ = ()
     def connection_made(self, transport: transports.DatagramTransport) -> None: ...  # type: ignore[override]
-    # addr can be a tuple[int, int] for some unusual protocols like socket.AF_NETLINK.
-    # Use tuple[str | Any, int] to not cause typechecking issues on most usual cases.
-    # This could be improved by using tuple[AnyOf[str, int], int] if the AnyOf feature is accepted.
-    # See https://github.com/python/typing/issues/566
-    def datagram_received(self, data: bytes, addr: tuple[str | Any, int]) -> None: ...
+    # addr varies by socket family and can be a tuple[str, int, int, int] for IPv6,
+    # tuple[int, int] for some unusual protocols like socket.AF_NETLINK, or other
+    # shapes. Keep this aligned with socket.recvfrom's return address type.
+    def datagram_received(self, data: bytes, addr: _RetAddress) -> None: ...
     def error_received(self, exc: Exception) -> None: ...
 
 class SubprocessProtocol(BaseProtocol):