Message219651
It occurred to me that the current patch I have is wrong and that using _Py_set_inheritable is wrong because EBADF can occur in the brute force version which in the case of _Py_set_inheritable raises an error which I am not sure is asynch signal safe. I could test ahead of time but that is a bit hacky. The most principled approach would be to extract either a common set_cloexec or set_inheritable function. If set_inheritable is done then I would have to report either a Windows error or an errno error which would be messy. I'm not sure where the best place to put the set_cloexec function would be. |
|
Date |
User |
Action |
Args |
2014-06-02 23:42:07 | sstewartgallus | set | recipients:
+ sstewartgallus, gregory.p.smith, pitrou, vstinner, neologix |
2014-06-02 23:42:07 | sstewartgallus | set | messageid: <1401752527.17.0.281293178984.issue21627@psf.upfronthosting.co.za> |
2014-06-02 23:42:07 | sstewartgallus | link | issue21627 messages |
2014-06-02 23:42:07 | sstewartgallus | create | |
|