Paul Ollis <pyt...@ollis.me.uk> added the comment:
> I thought that if this raises a (normal) exception, it always means that it > did not have overtaken the `fd`, i.e. never results in an unreferenced file > object which has taken ownership of `fd`. The current CPython implementation does not guard against this happening. Some incorrect combinations of arguments will definitely cause the problem. It is also possible that it could occur under other circumstances. > It this is not true right now, you are right that this is problematic. But > this should be simple to fix on the CPython side, right? I.e. to make sure > whenever some exception is raised here, even if some temporary file object > already was constructed, it will not close `fd`. It should be consistent in > this behavior, otherwise indeed, the semantics are broken. I agree. I think it should be fairly simple to fix for CPython. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue39318> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
