Author ezio.melotti
Recipients ezio.melotti, giampaolo.rodola, loewis, vstinner
Date 2009-02-03.14:01:48
SpamBayes Score 6.87857e-09
Marked as misclassified No
Message-id <1233669710.59.0.690566271747.issue5110@psf.upfronthosting.co.za>
In-reply-to
Content
> Problem: use different (encoding) rule for the display hook and for
> print() may disturb new users (Why does ">>> chr(...)" work whereas
> ">>> print(chr(...))" fails?).

This is the same behavior that Python2.x has (with the only difference
that Py2 always show the char as u'\uXXXX' if >0x7F whereas Py3 /tries/
to display it):
>>> unichr(0x0100)
u'\u0100'
>>> print unichr(0x0100)
UnicodeEncodeError: 'charmap' codec can't encode character u'\u0100' in
position 0: character maps to <undefined>
History
Date User Action Args
2009-02-03 14:01:50ezio.melottisetrecipients: + ezio.melotti, loewis, vstinner, giampaolo.rodola
2009-02-03 14:01:50ezio.melottisetmessageid: <1233669710.59.0.690566271747.issue5110@psf.upfronthosting.co.za>
2009-02-03 14:01:49ezio.melottilinkissue5110 messages
2009-02-03 14:01:48ezio.melotticreate