Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #47958 > unrolled thread

Re: Must we include urllib just to decode a URL-encoded string, when using Requests?

Started byRobert Kern <robert.kern@gmail.com>
First post2013-06-13 14:20 +0100
Last post2013-06-13 14:20 +0100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Must we include urllib just to decode a URL-encoded string, when using Requests? Robert Kern <robert.kern@gmail.com> - 2013-06-13 14:20 +0100

#47958 — Re: Must we include urllib just to decode a URL-encoded string, when using Requests?

FromRobert Kern <robert.kern@gmail.com>
Date2013-06-13 14:20 +0100
SubjectRe: Must we include urllib just to decode a URL-encoded string, when using Requests?
Message-ID<mailman.3191.1371129669.3114.python-list@python.org>
On 2013-06-13 14:05, Dotan Cohen wrote:
> I am using the Requests module to access remote URLs. Sometimes I need
> to URL-decode or URL-encode a string (via RFC 3986). Must I import
> urllib or urllib2 just to use their quote() and unquote() methods?

Yes. Do you think there is a problem with doing so?

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
  that is made terrible by our own mad attempt to interpret it as though it had
  an underlying truth."
   -- Umberto Eco

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web