You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dmitrin9 opened this issue
May 25, 2025
· 3 comments
Labels
3.13bugs and security fixes3.14bugs and security fixes3.15new features, bugs and security fixesdocsDocumentation in the Doc dirtopic-asynciotype-bugAn unexpected behavior, bug, or error
In 3.13 a feature where unix sockets are automatically cleaned up was added in asyncio. It was seen as a compatibility break but was recent enough that we could not do anything specifically about it at the time. We were able to come to the agreement however, that the change, being breaking, needed to be documented but wasn't.
Note that 3.12 is security-only so we will not change the docs for 3.12 (even if they are incorrect), sorry. We will however change them in 3.13+.
NVM, the feature is only 3.13+
picnixz
changed the title
asyncio.start_unix_server() cleanup_socket defaulting to true after 3.12 is not documented
asyncio.start_unix_server() cleanup_socket defaulting to true in 3.13 is not documented
May 25, 2025
3.13bugs and security fixes3.14bugs and security fixes3.15new features, bugs and security fixesdocsDocumentation in the Doc dirtopic-asynciotype-bugAn unexpected behavior, bug, or error
Documentation
In 3.13 a feature where unix sockets are automatically cleaned up was added in asyncio. It was seen as a compatibility break but was recent enough that we could not do anything specifically about it at the time. We were able to come to the agreement however, that the change, being breaking, needed to be documented but wasn't.
Relevant issue:
#133354
The text was updated successfully, but these errors were encountered: