[issue8024] upgrade to Unicode 5.2

Florent Xicluna added the comment: Merged with r79093 -- resolution: accepted -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue8024] upgrade to Unicode 5.2

Marc-Andre Lemburg added the comment: Amaury Forgeot d'Arc wrote: > > Amaury Forgeot d'Arc added the comment: > >> Looking closer at the patch, you also changed the unicodetype mappings >> and since this removes a lot of entries, it looks like the Unicode >> consortium either moved some mappi

[issue8024] upgrade to Unicode 5.2

Marc-Andre Lemburg added the comment: Florent Xicluna wrote: > > Florent Xicluna added the comment: > > The bug was a side-effect of the update. Code point "\u" is now assigned > to a printable character: > > ;TAI VIET LETTER LOW VO;Lo;0;L;N; > > And test_bigmem relies on

[issue8024] upgrade to Unicode 5.2

Amaury Forgeot d'Arc added the comment: > Looking closer at the patch, you also changed the unicodetype mappings > and since this removes a lot of entries, it looks like the Unicode > consortium either moved some mappings out of the UCD file into a > separate file or made some massive changes to

[issue8024] upgrade to Unicode 5.2

Florent Xicluna added the comment: The bug was a side-effect of the update. Code point "\u" is now assigned to a printable character: ;TAI VIET LETTER LOW VO;Lo;0;L;N; And test_bigmem relies on this code point being non-printable. I changed it for a char in the Low surrogate

[issue8024] upgrade to Unicode 5.2

Marc-Andre Lemburg added the comment: Florent Xicluna wrote: > > Florent Xicluna added the comment: > > Reverted in 3.x: it triggers some failures. > > Symptoms: > * repr('\uaaa') gives an empty string > * test_bigmem fails repr() for Unicode doesn't use the Unicode database. Are you sure

[issue8024] upgrade to Unicode 5.2

Florent Xicluna added the comment: Reverted in 3.x: it triggers some failures. Symptoms: * repr('\uaaa') gives an empty string * test_bigmem fails -- resolution: fixed -> accepted stage: committed/rejected -> commit review status: closed -> open _

[issue8024] upgrade to Unicode 5.2

Florent Xicluna added the comment: Done with r79059 and r79062. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue8024] upgrade to Unicode 5.2

Changes by Florent Xicluna : -- title: upgrade to Unicode 5.2? -> upgrade to Unicode 5.2 ___ Python tracker ___ ___ Python-bugs-list ma

[issue8024] upgrade to Unicode 5.2?

Marc-Andre Lemburg added the comment: Florent Xicluna wrote: > > Florent Xicluna added the comment: > >> So the Unicode database format itself has not changed ? > > No. The changes listed below have no impact afai-have-tested. Ok, so +1 for updating to 5.2. The files that have changed are

[issue8024] upgrade to Unicode 5.2?

Florent Xicluna added the comment: > So the Unicode database format itself has not changed ? No. The changes listed below have no impact afai-have-tested. - - - - - - - F. Unicode Character Database Changes The detailed listing of all ch

[issue8024] upgrade to Unicode 5.2?

Marc-Andre Lemburg added the comment: Florent Xicluna wrote: > > Florent Xicluna added the comment: > > It is just a matter of running "makeunicodedata" affter changing "5.1" -> > "5.2". > > It generates the 3 db files: > * Modules/unicodedata_db.h > * Modules/unicodename_db.h > * Object

[issue8024] upgrade to Unicode 5.2?

Florent Xicluna added the comment: It is just a matter of running "makeunicodedata" affter changing "5.1" -> "5.2". It generates the 3 db files: * Modules/unicodedata_db.h * Modules/unicodename_db.h * Objects/unicodetype_db.h Then you adjust the "expectedchecksum" in "Lib/test/test_unicoded

[issue8024] upgrade to Unicode 5.2?

Marc-Andre Lemburg added the comment: Have you checked how big the structural changes are between 5.2 and 5.1. If we only have to rerun the makeunicodedata.py script, then I'd be +1 on going with 5.2. Otherwise, I think it's better to wait another release before upgrading to the then latest

[issue8024] upgrade to Unicode 5.2?

Florent Xicluna added the comment: Excerpt of the release note: http://www.unicode.org/versions/Unicode5.2.0/ The Unicode Standard, Version 5.2, adds 6,648 characters and significantly improves the documentation of conformance requirements for the specification of normalization forms, canonic