RetroSearch Browse

Wed Mar 26 13:43:06 CET 2008 · https://mail.python.org/pipermail/python-dev/2008-March/078230.html

2008/3/26, Christian Heimes <lists at cheimes.de>:

> > I'm okay with bytearray not being subclassable in 2.6 as a temporary
>  > measure. I wouldn't want that to leak into 3.0 though, and I'd rather
>  > have it subclassable in 2.6 as well. I wonder why it doesn't work in
>  > 2.6 but does work in 3.0?
>
> This fix for the issue was easy once I noticed the cause of the problem
>
>  Modified: python/branches/trunk-bytearray/Objects/typeobject.c

So, now the byte object behaves equal in 2.6 and 3.0, right?

Thanks!

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/

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

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

[Python-Dev] Backport of bytearray type and io module