Amaury Forgeot d'Arc amauryfa at gmail.com
Fri Feb 1 15:18:39 CET 2013

• Previous message: [Python-Dev] Release or not release the GIL
• Next message: [Python-Dev] Release or not release the GIL
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

2013/2/1 Charles-François Natali <cf.natali at gmail.com>

> >> dup2(oldfd, newfd) closes oldfd.
> >
> > No, it doesn't close oldfd.
> >
> > It may close newfd if it was already open.
>
> (I guess that's what he meant).
>
> Anyway, only dup2() should probably release the GIL.
>
> One reasonable heuristic is to check the man page: if the syscall can
> return EINTR, then the GIL should be released.


Should the call be retried in the EINTR case?
(After a PyErr_CheckSignals)

-- 
Amaury Forgeot d'Arc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20130201/56c3ecb9/attachment.html>

---

• Previous message: [Python-Dev] Release or not release the GIL
• Next message: [Python-Dev] Release or not release the GIL
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list