[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

2015-09-30 Thread Shreevatsa R
Shreevatsa R added the comment: About the mismatch: of course it's probably not a good idea to change the parser (so that simply typing १२३४ in Python 3 code is like typing 1234), but how about changing the behaviour of int()? Not sure whether anyone should be relying on int(u'१२

[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

2015-09-30 Thread Shreevatsa R
Shreevatsa R added the comment: Minor difference, but the relevant function for int() is not quite isdigit(), e.g.: >>> import unicodedata >>> s = u'\u2460' >>> unicodedata.name(s) 'CIRCLED DIGIT ONE' >>> print

[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

2015-09-29 Thread Shreevatsa R
New submission from Shreevatsa R: Summary: This is about int(u'१२३४') == 1234. At https://docs.python.org/2/library/functions.html and also https://docs.python.org/3/library/functions.html the documentation for class int(x=0) class int(x, base=10) says (respectively):