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 vstinner
Recipients amaury.forgeotdarc, pitrou, santoso.wijaya, socketpair, vstinner
Date 2011-11-02.12:54:22
SpamBayes Score 1.86647e-05
Marked as misclassified No
Message-id <>
In-reply-to <>
> 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. 

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".
Date User Action Args
2011-11-02 12:54:23vstinnersetrecipients: + vstinner, amaury.forgeotdarc, pitrou, santoso.wijaya, socketpair
2011-11-02 12:54:22vstinnerlinkissue12939 messages
2011-11-02 12:54:22vstinnercreate