Steve Dower <steve.do...@python.org> added the comment:
> 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37549> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
