[issue6632] Include more fullwidth chars in the decimal codec

Changes by Ezio Melotti : -- nosy: +lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue6632] Include more fullwidth chars in the decimal codec

Ezio Melotti added the comment: Alexander, can this be closed or is there still something that should be done? -- ___ Python tracker ___ __

[issue6632] Include more fullwidth chars in the decimal codec

Changes by Ezio Melotti : -- nosy: +tchrist ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue6632] Include more fullwidth chars in the decimal codec

Changes by Stefan Krah : -- nosy: +skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue6632] Include more fullwidth chars in the decimal codec

Alexander Belopolsky added the comment: I wonder if the issues raised here can be neatly addressed by applying NFKC normalization before string to number conversion. This will convert full-width variants to ASCII and also eliminate digit/decimal differences. For example superscript and subs

[issue6632] Include more fullwidth chars in the decimal codec

Alexander Belopolsky added the comment: I wish I discovered this issue when I was working on #10557! Chances are I wouldn't have started a long python-dev thread rehashing the same issues as I see discussed here. In any case, in #10557, I replaced core uses of PyUnicode_EncodeDecimal() with

[issue6632] Include more fullwidth chars in the decimal codec

Raymond Hettinger added the comment: The moratorium only includes builtins and certainly does not apply to pure python modules (other implementations see those benefits immediately and it does not interfere with their getting caught-up). FWIW, I'm +1 on the basic idea. -- keywords:

[issue6632] Include more fullwidth chars in the decimal codec

Changes by Terry J. Reedy : -- keywords: +after moratorium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue6632] Include more fullwidth chars in the decimal codec

Terry J. Reedy added the comment: I believe this is covered by the PEP3003 3.2 change moratorium. -- nosy: +terry.reedy versions: +Python 3.3 -Python 2.7, Python 3.2 ___ Python tracker _

[issue6632] Include more fullwidth chars in the decimal codec

Marc-Andre Lemburg added the comment: Martin v. Löwis wrote: > > Martin v. Löwis added the comment: > >> The codec currently doesn't look at the base at all - and shouldn't >> need to: >> >> It simply converts input characters that have a decimal digit value >> associated with them, to the us

[issue6632] Include more fullwidth chars in the decimal codec

Martin v. Löwis added the comment: > The codec currently doesn't look at the base at all - and shouldn't > need to: > > It simply converts input characters that have a decimal digit value > associated with them, to the usual ASCII digits in preparation > for parsing them using the standard numb

[issue6632] Include more fullwidth chars in the decimal codec

Marc-Andre Lemburg added the comment: Martin v. Löwis wrote: > > Martin v. Löwis added the comment: > >> int()/float() use the decimal codec for numbers - this only supports >> base-10 numbers. For hex numbers, we'd need a new hex codec (only >> the encoder part, actually), otherwise, int('a'

[issue6632] Include more fullwidth chars in the decimal codec

Martin v. Löwis added the comment: > int()/float() use the decimal codec for numbers - this only supports > base-10 numbers. For hex numbers, we'd need a new hex codec (only > the encoder part, actually), otherwise, int('a') would start to return > 10. That's not true. PyUnicode_EncodeDecimal c

[issue6632] Include more fullwidth chars in the decimal codec

Marc-Andre Lemburg added the comment: Mark Dickinson wrote: > > I'm less concerned about decimal points and the like, and more bothered by > the fact that e.g., int(x, 16) accepts some, but not all, characters with > the Hex_Digit property. This seems counter to the intent of the Unicode >

[issue6632] Include more fullwidth chars in the decimal codec

Mark Dickinson added the comment: [Mark Dickinson] > Python's current support for localization in int and float seems > largely accidental, as far as I can tell. [MAL] > Not at all. [...] Apologies; 'accidental' was a poor choice of word here. > however, I did not look > at things like decim

[issue6632] Include more fullwidth chars in the decimal codec

Marc-Andre Lemburg added the comment: Mark Dickinson wrote: > Python's current support for localization in int and float seems largely > accidental, as far as I can tell. Not at all. The support for non-ASCII numeric characters in int() and float() is by design - however, I did not look at thi

[issue6632] Include more fullwidth chars in the decimal codec

Mark Dickinson added the comment: Python's current support for localization in int and float seems largely accidental, as far as I can tell. But I appreciate the argument that despite the current inconsistencies, we shouldn't add extra support without a standard to base it on. I'm not sure h

[issue6632] Include more fullwidth chars in the decimal codec

Antoine Pitrou added the comment: On the specific point of: > 2.1 some languages/alphabets use other chars (e.g. a comma or other > symbols) instead of the decimal point. I think it's not the job of the float() constructor to support it. Depending on the country, the comma has differen

[issue6632] Include more fullwidth chars in the decimal codec

Changes by Gabriel Genellina : -- nosy: +gagenellina ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue6632] Include more fullwidth chars in the decimal codec

Marc-Andre Lemburg added the comment: Ezio Melotti wrote: > > New submission from Ezio Melotti : > > The decimal codec only handles characters in the Nd (Number, decimal) > Unicode category and whitespaces [a]. It is used by int(), float(), > complex() and indirectly by Decimal(), Fraction() a

[issue6632] Include more fullwidth chars in the decimal codec

Mark Dickinson added the comment: The bit that most convinces me that *some* change is desirable is that (with py3k notation), int('７', 16) is legal but int('Ｆ', 16) is not. In an ideal world one might hope that the set of characters accepted by int(s, 16) would be the same as those characters

[issue6632] Include more fullwidth chars in the decimal codec

Changes by Eric Smith : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue6632] Include more fullwidth chars in the decimal codec

Changes by Ezio Melotti : -- nosy: +lemburg, loewis, marketdickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue6632] Include more fullwidth chars in the decimal codec

New submission from Ezio Melotti : The decimal codec only handles characters in the Nd (Number, decimal) Unicode category and whitespaces [a]. It is used by int(), float(), complex() and indirectly by Decimal(), Fraction() and possibly others. This works well only for plain digits (e.g. int(u'１２３