Guido van Rossum schrieb: > 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?
It *seems* like the comparison ops don't work correctly for subclasses. In general subclassing works but comparison of subclasses result in wrong results. It's probably easy to fix but I haven't figured it out yet. Christian _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com