[Python-Dev] Release or not release the GIL (original) (raw)

Richard Oudkerk shibturn at gmail.com
Fri Feb 1 14:08:01 CET 2013

On 01/02/2013 1:44am, Guido van Rossum wrote:

I'm guessing those system calls are just implemented by the kernel and cannot block for I/O, so it was deemed unnecessary to release the GIL around them. I don't mind changing that though, you can never know what happens when you make a system call.

close() can block, so I assume the same is true of dup2(), since dup2(oldfd, newfd) closes oldfd.

-- Richard

More information about the Python-Dev mailing list