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 lemburg
Recipients eric.smith, ezio.melotti, ggenellina, lemburg, loewis, mark.dickinson, pitrou
Date 2009-08-07.08:45:52
SpamBayes Score 2.5834515e-06
Marked as misclassified No
Message-id <4A7BE9BE.1010601@egenix.com>
In-reply-to <1249567474.38.0.367548603962.issue6632@psf.upfronthosting.co.za>
Content
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 
> standard.

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.

Any takers ?
History
Date User Action Args
2009-08-07 08:45:55lemburgsetrecipients: + lemburg, loewis, mark.dickinson, ggenellina, pitrou, eric.smith, ezio.melotti
2009-08-07 08:45:53lemburglinkissue6632 messages
2009-08-07 08:45:52lemburgcreate