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 senko
Recipients Ramchandra Apte, davide.rizzo, ezio.melotti, karlcow, kiilerix, krisys, maker, orsenthil, sandro.tosi, senko
Date 2013-07-06.10:08:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1373105292.78.0.518055708608.issue13359@psf.upfronthosting.co.za>
In-reply-to
Content
I vote for the parse method converting the spaces (and only the spaces) explicitly, for the following reasons:

* the spaces must be encoded for the server to accept them
* no user-encoded url will ever have spaces in them
* space quoting is idempotent: quote(quote(' ')) == quote(' ')
* if the user did get an exception from Request in case of invalid url containing the spaces, the only thing he or she can do is to quote the url string

Here's a patch implementing this. The change allows for any whitespace character in the selector part of the url (and in particular, '\n'), not only ' '.
History
Date User Action Args
2013-07-06 10:08:12senkosetrecipients: + senko, orsenthil, kiilerix, ezio.melotti, karlcow, sandro.tosi, maker, davide.rizzo, Ramchandra Apte, krisys
2013-07-06 10:08:12senkosetmessageid: <1373105292.78.0.518055708608.issue13359@psf.upfronthosting.co.za>
2013-07-06 10:08:12senkolinkissue13359 messages
2013-07-06 10:08:12senkocreate