This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients eric.smith, ezio.melotti, ggenellina, lemburg, loewis, mark.dickinson, pitrou
Date 2009-08-06.14:04:33
SpamBayes Score 4.089533e-05
Marked as misclassified No
Message-id <1249567474.38.0.367548603962.issue6632@psf.upfronthosting.co.za>
In-reply-to
Content
[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 decimal points, minus/plus signs, etc. at the
> time and only included support for numeric values associated
> with a number of code points, such as ½ for 1/2.

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 
standard.

[MAL]
> My suggestion is to wait for the Unicode locale project to collect
> locale based information on numeric formatting. [...]

Sounds fine to me.
History
Date User Action Args
2009-08-06 14:04:34mark.dickinsonsetrecipients: + mark.dickinson, lemburg, loewis, ggenellina, pitrou, eric.smith, ezio.melotti
2009-08-06 14:04:34mark.dickinsonsetmessageid: <1249567474.38.0.367548603962.issue6632@psf.upfronthosting.co.za>
2009-08-06 14:04:33mark.dickinsonlinkissue6632 messages
2009-08-06 14:04:33mark.dickinsoncreate