Message 84216 - 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	jhylton
Recipients	dmahn, jhylton
Date	2009-03-26.20:57:49
SpamBayes Score	6.4687584e-09
Marked as misclassified	No
Message-id	<1238101071.23.0.315592625717.issue5468@psf.upfronthosting.co.za>
In-reply-to

Content
I'm not sure I understand the part of the code that deals with binary strings. I agree the current behavior is odd. RFC 2396 says that non-ascii characters must be encoded as utf-8 and then percent escaped. In the test case you started with, you encoded b'\xa0\x24'. It doesn't seem like this should be allowed, since it is not valid utf-8.

I'm not sure I understand the part of the code that deals with binary
strings.  I agree the current behavior is odd.  RFC 2396 says that
non-ascii characters must be encoded as utf-8 and then percent escaped.
 In the test case you started with, you encoded b'\xa0\x24'.  It doesn't
seem like this should be allowed, since it is not valid utf-8.

History
Date	User	Action	Args
2009-03-26 20:57:51	jhylton	set	recipients: + jhylton, dmahn
2009-03-26 20:57:51	jhylton	set	messageid: <1238101071.23.0.315592625717.issue5468@psf.upfronthosting.co.za>
2009-03-26 20:57:50	jhylton	link	issue5468 messages
2009-03-26 20:57:49	jhylton	create