Walter Dörwald schrieb: > I have a patch against the py3k branch (http://bugs.python.org/1775604) > that adds UTF-32 codecs. On a narrow build it combines surrogate pairs > in the unicode object into one codepoint on encoding and creates > surrogate pairs for codepoints outside the BMP on decoding. > > Should I apply this to the py3k branch only, or do we want that for > Python 2.6 too (using str instead of bytes)?
If it's no effort, I would like to seem this on the trunk also. In general, I'm skeptical about the "new features only in 3k" strategy. Some features can be added easily with no backwards-compatibility issues in 2.x, and would have normally been added to the next major 2.x release without much discussion. Regards, Martin _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
