RetroSearch Browse

Thu Apr 22 01:05:36 CEST 2010 · https://mail.python.org/pipermail/python-dev/2010-April/099622.html

Le jeudi 22 avril 2010 00:21:02, vous avez écrit :
> Victor Stinner wrote:
> > I will be very sad if someone ask me to keep bytearray filename support
> > in 3.2 because I opened a lot of issues about surrogates and I would make
> > my work more diffcult :-(
> 
> I don't have an opinion one way or the other regarding bytearray, but
> even if you deprecated it rather than dropping it, couldn't you just add
> the surrogate support for the Unicode path and leave the bytecode path
> with the legacy behaviour?

Yes, we can do everything. But does it really have a sense? No Python function 
using filenames return a bytearray object. Example: os.listdir() and os.walk() 
result type is bytes or str.

Changing PyUnicode_FSConverter() is trivial, but the problem is in the 
function calling PyUnicode_FSConverter(). The caller have to support byte and 
bytearray. Antoine proposed to convert bytearray to bytes to ensure that 
PyUnicode_FSConverter() result is a bytes object. But in this case, we still 
need also to fix ntpath, ,posixpath and macpath modules to support bytearray.

-- 
Victor Stinner
http://www.haypocalc.com/

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

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

[Python-Dev] Reject bytearray filename in Python 3.2