➜

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 belopolsky
Recipients belopolsky, cvrebert, eric.araujo, eric.smith, ezio.melotti, lemburg, mark.dickinson, skrah, vstinner
Date 2013-06-12.05:32:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371015137.36.0.535918556898.issue10581@psf.upfronthosting.co.za>
In-reply-to
Content 
It looks like we a approaching consensus on some points:

1. Mixed script numerals should be disallowed.
2. '\N{MINUS SIGN}' should be accepted as an alternative to '\N{HYPHEN-MINUS}'

Open question: should we accept fullwidth + and -, sub/superscript variants etc.?  I believe rather than debating variant codepoints one by one, we should consider applying NFKC (compatibility) normalization to unicode strings to be interpreted as numbers.  This would allow parsing strings like this:

>>> float(normalize('NFKC', '\N{FULLWIDTH HYPHEN-MINUS}\N{DIGIT ONE FULL STOP}\N{FULLWIDTH DIGIT TWO}'))
-1.2
History
Date User Action Args
2013-06-12 05:32:17belopolskysetrecipients: + belopolsky, lemburg, mark.dickinson, vstinner, eric.smith, ezio.melotti, eric.araujo, cvrebert, skrah
2013-06-12 05:32:17belopolskysetmessageid: <1371015137.36.0.535918556898.issue10581@psf.upfronthosting.co.za>
2013-06-12 05:32:17belopolskylinkissue10581 messages
2013-06-12 05:32:16belopolskycreate