Message 102077 - 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	lemburg
Recipients	dangra, ezio.melotti, lemburg, sjmachin
Date	2010-04-01.08:46:32
SpamBayes Score	2.912171e-06
Marked as misclassified	No
Message-id	<4BB45D66.5080404@egenix.com>
In-reply-to	<1270110827.02.0.3072878206.issue8271@psf.upfronthosting.co.za>

Content
Ezio Melotti wrote: > > Ezio Melotti <ezio.melotti@gmail.com> added the comment: > > Here is an incomplete patch. It seems to solve the problem but I still have to add more tests and check it better. Thanks. Please also check whether it's worthwhile unrolling those loops by hand. > I also wonder if the sequences with the first byte in range F5-FD (start of 4/5/6-byte sequences, restricted by RFC 3629) should behave in the same way. Right now they just "eat" the following 4/5/6 chars without checking. I think we need to do this all the way, even though 5 and 6 byte sequences are not used at the moment.

Ezio Melotti wrote:
> 
> Ezio Melotti <ezio.melotti@gmail.com> added the comment:
> 
> Here is an incomplete patch. It seems to solve the problem but I still have to add more tests and check it better.

Thanks. Please also check whether it's worthwhile unrolling those
loops by hand.

> I also wonder if the sequences with the first byte in range F5-FD (start of 4/5/6-byte sequences, restricted by RFC 3629) should behave in the same way. Right now they just "eat" the following 4/5/6 chars without checking.

I think we need to do this all the way, even though 5 and 6 byte
sequences are not used at the moment.

History
Date	User	Action	Args
2010-04-01 08:46:34	lemburg	set	recipients: + lemburg, sjmachin, ezio.melotti, dangra
2010-04-01 08:46:32	lemburg	link	issue8271 messages
2010-04-01 08:46:32	lemburg	create