[GvR] > I believe the issue of whether and how to backport bytes > (and bytearray?) from 3.0 to 2.6 has come up before, but > I don't think we've come to any kind of conclusion.
My recommendation is to leave it out of 2.6. Not every 3.0 concept has to be backported. This particular one doesn't have a straight-forward integration. It duplicates some existing functionality and in general doesn't make life better for the 2.6 coder. The only benefit I can see is that it lets you write code that is a step closer to 3.0; however, it has not been our goal to write one piece of code that runs under both major releases. I think both 2.x and 3.0 are better served if 2.x cleanly stays with the str/uncode model and 3.0 sticks with the bytes/text model. Commingling the two muddies the waters and conflates the distinctions. I think it best to make that jump all at once. Multiple-ways-to-do-it should not be the motto for 2.6. Instead, let's provide the best transition tools possible and keep both 2.6 and 3.0 as clean as possible (no duplicative or half-intergrated functionality). Raymond _______________________________________________ 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
