This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients ajaksu2, facundobatista, hthompson, lemburg, loewis, vstinner
Date 2009-02-12.12:32:18
SpamBayes Score 4.106656e-09
Marked as misclassified No
Message-id <499416D0.3060006@egenix.com>
In-reply-to <1234439365.49.0.00501762992646.issue637094@psf.upfronthosting.co.za>
Content
On 2009-02-12 12:49, STINNER Victor wrote:
> STINNER Victor <victor.stinner@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.
History
Date User Action Args
2009-02-12 12:32:20lemburgsetrecipients: + lemburg, loewis, facundobatista, vstinner, ajaksu2, hthompson
2009-02-12 12:32:18lemburglinkissue637094 messages
2009-02-12 12:32:18lemburgcreate