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 a.badger
Recipients a.badger, janssen
Date 2008-09-30.18:11:22
SpamBayes Score 1.4780638e-09
Marked as misclassified No
Message-id <1222798284.52.0.823109205463.issue3991@psf.upfronthosting.co.za>
In-reply-to
Content
The purpose of such a function would be to take something that is not a
valid uri but 1) is a common way of expressing the way to get to the
resource and 2) follows certain rules and turns that into something that
is a valid uri.  non-ASCii strings in the path are a good example of
this since there is a well defined method to encode the strings into the
URL if you are given a character encoding to apply to it.

My first, naive thought is that if the input can be parsed by
urlparse(), then there is a very good chance that we have the ability to
escape the string properly.  Looking at the invalid uri that I gave, for
instance, if you additionally specified an encoding for the path element
there's no reason a function couldn't do the escaping.

What are example inputs that you are concerned about?  I'll see if I can
come up with code that works with them.
History
Date User Action Args
2008-09-30 18:11:24a.badgersetrecipients: + a.badger, janssen
2008-09-30 18:11:24a.badgersetmessageid: <1222798284.52.0.823109205463.issue3991@psf.upfronthosting.co.za>
2008-09-30 18:11:23a.badgerlinkissue3991 messages
2008-09-30 18:11:22a.badgercreate