[issue45819] Avoid releasing the GIL in nonblocking socket operations

Change by jakirkham : -- nosy: +jakirkham ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45819] Avoid releasing the GIL in nonblocking socket operations

Christian Heimes added the comment: Do POSIX and Windows APIs guarantee that operations on a nonblocking socket can never ever block? We cannot safely keep the GIL unless you can turn "nonblocking socket operations by definition shouldn't block" into "standard guarantees that nonblocking

[issue45819] Avoid releasing the GIL in nonblocking socket operations

Raymond Hettinger added the comment: +1 There is almost no upside for the current behavior. -- nosy: +rhettinger ___ Python tracker ___

[issue45819] Avoid releasing the GIL in nonblocking socket operations

Change by Jim Crist-Harif : -- components: +asyncio -C API nosy: +asvetlov, yselivanov ___ Python tracker ___ ___ Python-bugs-list

[issue45819] Avoid releasing the GIL in nonblocking socket operations

Change by Jim Crist-Harif : -- keywords: +patch pull_requests: +27822 stage: -> patch review pull_request: https://github.com/python/cpython/pull/29579 ___ Python tracker ___

[issue45819] Avoid releasing the GIL in nonblocking socket operations

New submission from Jim Crist-Harif : In https://bugs.python.org/issue7946 an issue with how the current GIL interacts with mixing IO and CPU bound work. Quoting this issue: > when an I/O bound thread executes an I/O call, > it always releases the GIL. Since the GIL is released, a CPU bound