RetroSearch Browse

Mon Apr 19 22:55:39 CEST 2010 · http://mail.python.org/pipermail/python-dev/2010-April/099573.html

> I'm working on surrogates in filenames on Linux (more generally on BSD and 
> UNIX OS) to support undecodable filenames, see PEP 383. Amaury told me that I 
> only fixed the non-Windows versions (I fixed subprocess about the current 
> directory and _ctypes.dlopen()), but it doesn't work on Windows.
> 
> It's a choice, I didn't want to patch Windows because I know that Windows use 
> unicode internally. I consider that developers using Python3 should use 
> unicode on Windows, and byte or unicode+surrogates on other OS.
> 
> I don't know well Windows API, and so I would like your opinion about that ;-)

Can you please elaborate what the specific issue is? I completely fail
to see what byte strings have to do with surrogate codes. AFAICT, on
Windows, you can just use surrogate codes at the APIs, and be done.

Regards,
Martin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2010-April/099573.html below:

[Python-Dev] Support byte string API of Windows in Python3?