➜

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 loewis
Recipients loewis, mgiuca
Date 2008-07-06.16:54:34
SpamBayes Score 0.0001619189
Marked as misclassified No
Message-id <4870F8C9.8080306@v.loewis.de>
In-reply-to <1215355930.42.0.79499861143.issue3300@psf.upfronthosting.co.za>
Content 
> RFC 3986 states that the percent-encoded byte
> values should be decoded as UTF-8.

Where precisely do you read such a SHOULD requirement?
Section 2.5 elaborates that the local encoding (of the
resource) is typically used, ignoring cases where URIs
are constructed on the client system (such scenario is
simply ignored in the RFC).

The last paragraph in section 2.5 is the only place that
seems to imply a SHOULD requirement (although it doesn't
use the keyword); this paragraph only talks about new URI
schemes. Unfortunately, for http, the encoding is of
characters is unspecified (this is somewhat solved by the
introduction of IRIs).
History
Date User Action Args
2008-07-06 16:54:36loewissetspambayes_score: 0.000161919 -> 0.0001619189
recipients: + loewis, mgiuca
2008-07-06 16:54:35loewislinkissue3300 messages
2008-07-06 16:54:34loewiscreate