On Thu, Sep 1, 2016, at 18:28, Steve Dower wrote: > This is a raw (bytes) IO class that requires text to be passed encoded > with utf-8, which will be decoded to utf-16-le and passed to the Windows APIs. > Similarly, bytes read from the class will be provided by the operating > system as utf-16-le and converted into utf-8 when returned to Python. What happens if a character is broken across a buffer boundary? e.g. if someone tries to read or write one byte at a time (you can't do a partial read of zero bytes, there's no way to distinguish that from an EOF.) Is there going to be a higher-level text I/O class that bypasses the UTF-8 encoding step when the underlying bytes stream is a console? What if we did that but left the encoding as mbcs? I.e. the console is text stream that can magically handle characters that aren't representable in its encoding. Note that if anything does os.read/write to the console's file descriptors, they're gonna get MBCS and there's nothing we can do about it.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4