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).
The issue can't be fixed in
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
STINNER Victor victor.stin...@haypocalc.com added the comment:
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
Marc-Andre Lemburg m...@egenix.com added the comment:
On 2009-02-12 14:22, STINNER Victor wrote:
STINNER Victor victor.stin...@haypocalc.com added the comment:
Python3 fixes the print statement to be a function, which allows
much better extensibility of the concept.
You can have the same
Daniel Diniz aja...@gmail.com added the comment:
Not sure it's still important after 3.0 release. Confirmed in trunk:
import codecs
class X:
def __unicode__(self):
print 'unicode'
return u'unicode'
def __str__(self):
print 'str'
return 'str'
x=X()
f =
