On Fri, Sep 6, 2013, at 13:04, Chris Angelico wrote: > On Sat, Sep 7, 2013 at 2:59 AM, <random...@fastmail.us> wrote: > > Incidentally, how does all this interact with ctypes unicode_buffers, > > which slice as strings and must be UTF-16 on windows? This was fine > > pre-FSR when unicode objects were UTF-16, but I'm not sure how it would > > work now. > > That would be pre-FSR *with a Narrow build*, which was the default on > Windows but not everywhere. But I don't know or use ctypes, so an > answer to your actual question will have to come from someone else.
I did a couple tests - it works as well as can be expected for reading, but completely breaks for writing (due to sequence size checks not matching) -- https://mail.python.org/mailman/listinfo/python-list
