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


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

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

Started byDotan Cohen <dotancohen@gmail.com>
First post2013-06-13 16:25 +0300
Last post2013-06-13 16:25 +0300
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? Dotan Cohen <dotancohen@gmail.com> - 2013-06-13 16:25 +0300

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

FromDotan Cohen <dotancohen@gmail.com>
Date2013-06-13 16:25 +0300
SubjectRe: Must we include urllib just to decode a URL-encoded string, when using Requests?
Message-ID<mailman.3192.1371129909.3114.python-list@python.org>
On Thu, Jun 13, 2013 at 4:20 PM, Robert Kern <robert.kern@gmail.com> wrote:
> Yes. Do you think there is a problem with doing so?
>

I'm pretty sure that Requests will use either urllib or urllib2,
depending on what is available on the server. I would like to use
whatever Requests is currently using, rather than import the other.
Can I tell which library Requests is currently using and use that?

--
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com

[toc] | [standalone]


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


csiph-web