This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients Jeffrey.Kintscher, ZackerySpytz, daveb, eryksun, josh.r, lukasz.langa, ned.deily, paul.moore, steve.dower, tim.golden, vstinner, xflr6, zach.ware
Date 2019-07-29.16:10:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> What 3.7.3 does is to skip calling _Py_set_inheritable for all files of type FILE_TYPE_CHAR

It sounds like we should probably revert to the middle ground, and skip _raising the error_ if _Py_set_inheritable for files of type FILE_TYPE_CHAR.

As Victor pointed out, the docs already call out the special case in Windows. Since this applies to Windows 7, which will be EOL only a couple months after 3.8's release, I think it's fine to have the slightly less secure behavior and just suppress the error.
Date User Action Args
2019-07-29 16:10:09steve.dowersetrecipients: + steve.dower, paul.moore, vstinner, tim.golden, ned.deily, lukasz.langa, zach.ware, eryksun, josh.r, xflr6, ZackerySpytz, Jeffrey.Kintscher, daveb
2019-07-29 16:10:09steve.dowersetmessageid: <>
2019-07-29 16:10:09steve.dowerlinkissue37549 messages
2019-07-29 16:10:09steve.dowercreate