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


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

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

Started byBurak Arslan <burak.arslan@arskom.com.tr>
First post2013-06-13 16:44 +0300
Last post2013-06-13 16:44 +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? Burak Arslan <burak.arslan@arskom.com.tr> - 2013-06-13 16:44 +0300

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

FromBurak Arslan <burak.arslan@arskom.com.tr>
Date2013-06-13 16:44 +0300
SubjectRe: Must we include urllib just to decode a URL-encoded string, when using Requests?
Message-ID<mailman.3196.1371131676.3114.python-list@python.org>
On 06/13/13 16:25, Dotan Cohen wrote:
> 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?
>

paste this to your python console, it'll show you what modules requests 
imports:


import sys
p = set(sys.modules)
import requests
for m in sorted(set(sys.modules) - p):
   print(m)


burak

[toc] | [standalone]


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


csiph-web