https://github.com/python/cpython/commit/fc297b4ba4c61febeb2d8f5d718f2955c6bbea0a commit: fc297b4ba4c61febeb2d8f5d718f2955c6bbea0a branch: main author: Alek Kowalczyk <[email protected]> committer: kumaraditya303 <[email protected]> date: 2024-06-24T08:35:02Z summary:
gh-112169: Documented getaddrinfo/getnameinfo default loop executor usage and implications. (#112191) Co-authored-by: Guido van Rossum <[email protected]> Co-authored-by: Kumar Aditya <[email protected]> Co-authored-by: Carol Willing <[email protected]> files: M Doc/library/asyncio-eventloop.rst diff --git a/Doc/library/asyncio-eventloop.rst b/Doc/library/asyncio-eventloop.rst index 374e789e91e790..1d79f78e8e1b67 100644 --- a/Doc/library/asyncio-eventloop.rst +++ b/Doc/library/asyncio-eventloop.rst @@ -1155,6 +1155,14 @@ DNS Asynchronous version of :meth:`socket.getnameinfo`. +.. note:: + Both *getaddrinfo* and *getnameinfo* internally utilize their synchronous + versions through the loop's default thread pool executor. + When this executor is saturated, these methods may experience delays, + which higher-level networking libraries may report as increased timeouts. + To mitigate this, consider using a custom executor for other user tasks, + or setting a default executor with a larger number of workers. + .. versionchanged:: 3.7 Both *getaddrinfo* and *getnameinfo* methods were always documented to return a coroutine, but prior to Python 3.7 they were, in fact, _______________________________________________ Python-checkins mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-checkins.python.org/ Member address: [email protected]
