Martin v. Löwis added the comment: Am 14.03.13 03:31, schrieb Piotr Dobrogost: > forces programs which would like to open a file being opened at the > same time by Python code (by means of built-in open() or os.open() > with default arguments) to either use O_TEMPORARY when using msvcrt > or to go low level and use CreateFile() Win32 API function with > FILE_SHARE_DELETE flag. Are we ok with it?
That's why I was asking for an actual patch. The proposed change may well not be implementable. If os.open continues to create CRT handles, a way needs to be found to get a CRT handle that as the FILE_SHARE_DELETE bit set. An alternative approach could be that os.open stops creating CRT handles, and directly uses OS handles. The problem with that is that stdin/stdout/stderr would stop being 0/1/2, which is not acceptable. An alternative solution to that could be that we introduce a notion of "python io handles", parallel, but indepedendent from CRT handles. And so on. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15244> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
