[issue3811] Update Unicode database to 5.1.0

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > The control characters? Indeed, also the private-use characters. test_unicode explicitly comments that the test is about unassigned characters, although I don't understand the purpose of that test (it then also tests a surrogate character,

[issue3811] Update Unicode database to 5.1.0

Changes by Guido van Rossum <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11461/unnamed ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3811] Update Unicode database to 5.1.0

Guido van Rossum <[EMAIL PROTECTED]> added the comment: 2008/9/10 Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: > Code point 0x0370 is now a printable character. > r66381 corrected the failures by simply changing it to 0x0378, until the > next unicodedata upgrade... > I wonder if there is a value tha

[issue3811] Update Unicode database to 5.1.0

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Code point 0x0370 is now a printable character. r66381 corrected the failures by simply changing it to 0x0378, until the next unicodedata upgrade... I wonder if there is a value that is guaranteed to stay non-printable. -- nosy

[issue3811] Update Unicode database to 5.1.0

Daniel Diniz <[EMAIL PROTECTED]> added the comment: #66363 breaks test_unicode and test_format on 3.0. -- nosy: +ajaksu2 versions: +Python 3.0 ___ Python tracker <[EMAIL PROTECTED]> __

[issue3811] Update Unicode database to 5.1.0

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > That's unfortunate -- perhaps the 2.6 flag and data can be brought in > line, to make future merges easier? I thought of that, however, merging the databases themselves would still not be possible: the 3.0 database has the flags set in man

[issue3811] Update Unicode database to 5.1.0

Guido van Rossum <[EMAIL PROTECTED]> added the comment: 2008/9/10 Martin v. Löwis <[EMAIL PROTECTED]>: > I have now committed the change as r66362 (including the missing > documentation updates), and ported it to 3.0 as r66363 (where I had to > change the flag value and regenerate the data, as th

[issue3811] Update Unicode database to 5.1.0

Changes by Guido van Rossum <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11458/unnamed ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3811] Update Unicode database to 5.1.0

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: I have now committed the change as r66362 (including the missing documentation updates), and ported it to 3.0 as r66363 (where I had to change the flag value and regenerate the data, as the flag 0x100 was already taken). -- resolutio

[issue3811] Update Unicode database to 5.1.0

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: Reviewed the patch: looks fine to me. One nit: the unicodedata module doc-string must be updated to 5.1.0 as well. Ditto for the documentation. -- nosy: +lemburg ___ Python tracker <[EMAIL PR

[issue3811] Update Unicode database to 5.1.0

Fredrik Lundh <[EMAIL PROTECTED]> added the comment: The patch looks fine to me (assuming that I didn't miss something critical hidden among the large table diffs). (I'd probably named the "NODELTA" flag after what it is rather than what it isn't, but I cannot think of a short replacement righ

[issue3811] Update Unicode database to 5.1.0

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Guido, would you like to review? -- assignee: effbot -> gvanrossum nosy: +gvanrossum ___ Python tracker <[EMAIL PROTECTED]> _

[issue3811] Update Unicode database to 5.1.0

Changes by Martin v. Löwis <[EMAIL PROTECTED]>: -- keywords: +needs review ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-li

[issue3811] Update Unicode database to 5.1.0

Changes by Martin v. Löwis <[EMAIL PROTECTED]>: -- keywords: +patch -needs review ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-

[issue3811] Update Unicode database to 5.1.0

New submission from Martin v. Löwis <[EMAIL PROTECTED]>: This is a patch to update the Unicode database. It's mostly the imported data, but there were two code changes: - 5.1 changes the "mirrored" property for a character (U+0F3A), and the delta-to-3.2 code did not support that. I added a field