Message92984
| Author |
loewis |
| Recipients |
eric.smith, ezio.melotti, ggenellina, lemburg, loewis, mark.dickinson, pitrou |
| Date |
2009年09月22日.11:35:43 |
| SpamBayes Score |
0.0004009219 |
| Marked as misclassified |
No |
| Message-id |
<4AB7DD06.2040800@v.loewis.de> |
| In-reply-to |
<4A7BE9BE.1010601@egenix.com> |
| Content |
> 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 could happily accept hexdigits,
and int(u'a') would still be rejected. In fact, PyUnicode_EncodeDecimal
*already* accepts arbitrary Latin-1 characters, whether they represent
digits or not. I suppose this is to support non-decimal bases, so it
would only be consequential to widen this to all characters that
reasonably have the Hex_Digit property (although I'm unsure which ones
are excluded at the moment). |
|