A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2008-January/076534.html below:

[Python-Dev] [python] Re: [Python-checkins] r60283

[Python-Dev] [python] Re: [Python-checkins] r60283 - in python/trunk: Include/longintrepr.h Include/longobject.h Include/unicodeobject.h Misc/NEWS Modules/_fileio.c Objects/longobject.c Objects/unicodeobject.c setup.py [Python-Dev] [python] Re: [Python-checkins] r60283 - in python/trunk: Include/longintrepr.h Include/longobject.h Include/unicodeobject.h Misc/NEWS Modules/_fileio.c Objects/longobject.c Objects/unicodeobject.c setup.pyMichael Foord fuzzyman at voidspace.org.uk
Sat Jan 26 18:57:23 CET 2008
Guido van Rossum wrote:
> On Jan 26, 2008 1:16 AM, Raymond Hettinger <python at rcn.com> wrote:
>   
>> Are you planning to backport bytearrays?
>> I thought we had clearly decided to *not* backport any of the text/bytes model so that the
>> Py2.6 string/unicode model remained pure.
>>     
>
> 'bytearray' is a separate issue. It's a brand new type: a *mutable*
> byte array. Its status as a built-in and completely different API
> makes it much more convenient than using the old array module.
> Introducing bytearray is not going to disturb the balance between
> str/bytes/unicode.
>   
I'm looking forward to having a native mutable bytes type in Python 2.x.

Michael Foord
More information about the Python-Dev mailing list

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