Antoine Pitrou <pit...@free.fr> added the comment: > Just to be clear, I'm not at all criticizing the current GIL > implementation, there's been a great work done on it. > I'm just saying that releasing and re-acquiring the GIL around fast > syscalls is probaly not a good idea.
If these syscalls aren't likely to yield control to another thread, then I agree there's no point in releasing the GIL around them. (but is it the case that they are always fast? for example, how about dup() on a network file system? or is it indifferent?) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11382> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
