Marc-Andre Lemburg <m...@egenix.com> added the comment: On 2009-02-12 12:49, STINNER Victor wrote: > STINNER Victor <victor.stin...@haypocalc.com> added the comment: > > ajaksu2> Not sure it's still important after 3.0 release. > > Python2 has too much issues related to unicode. It's easier to switch > to Python3 which use unicode by default for most functions (eg. > print).
I don't agree with that statement. Python3 has better Unicode I/O support, but apart from that it's pretty much the same show. > The issue can't be fixed in Python2 without breaking the compatibility > (introduce regression). I think that the issue is fixed in Python3. Python3 fixes the "print" statement to be a function, which allows much better extensibility of the concept. You can have the same in Python2 with a little effort: just create your own myprint() function and have it process Unicode in whatever way you want. _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue637094> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
