2008/3/26, Christian Heimes email@example.com:
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
So, now the byte object behaves equal in 2.6 and 3.0, right?