Message 124251 - Python tracker

➜

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	Arfrever, barry, belopolsky, ezio.melotti, jhalcrow, lemburg, loewis, pitrou, valhallasw, vstinner
Date	2010-12-17.19:17:47
SpamBayes Score	2.608881e-10
Marked as misclassified	No
Message-id	<AANLkTimX6RhopEjnnjooWQg_QQsGffHfW8gLJaN3A192@mail.gmail.com>
In-reply-to	<4D0BB515.6090602@v.loewis.de>

Content
On Fri, Dec 17, 2010 at 2:08 PM, Martin v. Löwis <report@bugs.python.org> wrote: .. >> As far as I (and a two-line script) can tell >> the maximum length of a canonical decomposition of a character is 4. > > Even better - so allowing for 20 characters should be safe. I don't disagree, but the number of "break" and "continue" statements before cskipped++ makes me nervous. This said, I am going to add test cases from the first post to test_unicodedata (I think it is a better place than test_normalise because the latter is skipped by default) and commit. Improving the algorithm is a separate issue.

On Fri, Dec 17, 2010 at 2:08 PM, Martin v. Löwis <report@bugs.python.org> wrote:
..
>> As far as I (and a two-line script) can tell
>> the maximum length of a canonical decomposition of a character is 4.
>
> Even better - so allowing for 20 characters should be safe.

I don't disagree, but the number of "break" and "continue" statements
before cskipped++ makes me nervous.  This said, I am going to  add
test cases from the first post to test_unicodedata (I think it is a
better place than test_normalise because the latter is skipped by
default) and commit.

Improving the algorithm is a separate issue.

History
Date	User	Action	Args
2010-12-17 19:17:48	belopolsky	set	recipients: + belopolsky, lemburg, loewis, barry, pitrou, vstinner, ezio.melotti, Arfrever, jhalcrow, valhallasw
2010-12-17 19:17:47	belopolsky	link	issue10254 messages
2010-12-17 19:17:47	belopolsky	create