STINNER Victor <victor.stin...@haypocalc.com> added the comment: > Instead of rewriting your own RawIO implementation, why not use > _open_osfhandle?
I don't know yet what is the best approach. One important point is to keep the HANDLE, to be able to manipulate the open file using the Windows API (e.g. call WriteFile instead of write). I propose a RawIO to call directly the Windows API: file.write() would call directly WriteFile() instead of the POSIX wrapper (write()). We may use it to implement new features like async I/O on Windows (e.g. WriteFileEx). Modules/_multiprocessing/win32_functions.c exposes already some low-level Windows functions like WriteFile(). We may reuse the RawIO to offer an object oriented API for the Windows multiprocessing pipes. Such RawIO would have extra methods, maybe a file.WriteFile() method to give access to extra options like "overlapped". ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12939> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
