[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Amaury Forgeot d'Arc added the comment: Yes, my patch is entirely contained in the one from issue1571184. I mark this one as a duplicate, and will review and update the other. -- dependencies: -Generate numeric/space/linebreak from Unicode database. resolution: -> duplicate status: op

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Martin v. Löwis added the comment: Notice that this is a duplicate of the longstanding issue1571184, which has a patch that is more comprehensive than the one proposed here. So rather than accepting Amaury's patch, I'd prefer to see Anders' patch reviewed, and revised as necessary. -- d

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Vernon Cole added the comment: Wow! Quick response! My outstanding bug on IronPython has been hanging out there since August of last year. I don't really want to try compiling the standard library on my laptop, but I do want to fully test my code soon. What is the first place I can expect to s

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Amaury Forgeot d'Arc added the comment: Right. Actually unicodetype_db.h is the one included in unicodectype.c, I moved my script into makeunicodedata.py. Here is a new patch. The code generated for _PyUnicode_ToNumeric is the same as before (except for some tabs), see the old patch if you want

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Benjamin Peterson added the comment: Wouldn't it make more sense to move this into unicode_db.h? -- nosy: +benjamin.peterson, loewis ___ Python tracker ___ __

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Amaury Forgeot d'Arc added the comment: The _PyUnicode_ToNumeric() function was not in line with the unicode database. Here is a new version of this function, together with the script to generate its code. -- keywords: +needs review, patch nosy: +amaury.forgeotdarc Added file: http://bu

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

Ezio Melotti added the comment: Python 2.6 and all the following versions use the Unicode database version 5.1.0 [1] (unicodedata.unidata_version). The numeric value is in the database for all the codepoints from U+2185 to U+2188 (included), so the problem shouldn't be there. [1]: ftp://ftp.un

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

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

[issue6383] error in unicodedata.numeric(u"\u2187") and 2188

New submission from Vernon Cole : I am making a demo program, a class which is a subset of int, which implements a partial implementation of PEP313 (Roman numeral literals). I discover that my conversion routines fail for values > 5 due to an error in unicodedata for the two code points 2187