[issue11833] ord() doesn't show complete UNICODE

2011-04-11 Thread Ezio Melotti
Ezio Melotti added the comment: The problem is not with ord() but with the stdin encoding used by the windows terminal. If you write a non-ASCII character (e.g. '¥') in the windows terminal with Python 2 without using the u'' prefix, it will be encoded with the encoding specified by sys.stdin

[issue11833] ord() doesn't show complete UNICODE

2011-04-11 Thread Alec Taylor
Alec Taylor added the comment: Python 2.7.1, Win7 64-bit -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue11833] ord() doesn't show complete UNICODE

2011-04-11 Thread Ezio Melotti
Ezio Melotti added the comment: For the chars you pasted, on Python 3 I get: >>> ord('—') # U+2014 EM DASH 8212 >>> ord('¥') # U+00A5 YEN SIGN 165 If I type alt+8212 I get '—' and if I type alt+0165 I get '¥'. What version of Python are you using and on what OS? -- nosy: +ezio.melott

[issue11833] ord() doesn't show complete UNICODE

2011-04-11 Thread Alec Taylor
New submission from Alec Taylor : Unfortunately ord() doesn't show complete UNICODE. This can cause incorrectness problems. >>> ord('—') 151 >>> ord('¥') 165 Proof: Type Alt+0151, then type Alt+151. They should give you — and ù respectively. Please correct the UNICODE numbering. Thanks, Al