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 lemburg
Recipients lemburg, loewis, pitrou, vstinner
Date 2010-04-21.20:44:54
SpamBayes Score 4.724571e-08
Marked as misclassified No
Message-id <4BCF63F9.8050701@egenix.com>
In-reply-to <1271852937.17.0.825806652857.issue8485@psf.upfronthosting.co.za>
Content
Antoine Pitrou wrote:
> 
> Antoine Pitrou <pitrou@free.fr> added the comment:
> 
> Or perhaps the bytearray can be converted to a bytes object. This is not optimal performance-wise but is unlikely to make a difference in real-world code (if you are passing a filename to an external API, chances are some IO will occur which will dwarf the cost of creating a separate bytes object).
> 
> But I agree that supporting bytearrays in filename-taking functions, while "nice" from a consistency point of view, isn't really useful in practice. So I would be ok to remove that support if it simplifies (or avoids complexifying) the logic for those functions.

+1

bytearrays are basically the remains of the attempt to use mutable
byte string objects in Python 3.x. They may gain some usefulness
in the future, but I doubt that this will be in the area of filenames.
History
Date User Action Args
2010-04-21 20:44:55lemburgsetrecipients: + lemburg, loewis, pitrou, vstinner
2010-04-21 20:44:54lemburglinkissue8485 messages
2010-04-21 20:44:54lemburgcreate