Re: [BangPypers] Https and http difference in behaviour urllib2

2012-05-08 Thread Baiju M
This change reflected in the website after the commit I pointed out. On Tue, May 8, 2012 at 8:08 PM, Vishal wrote: > http://docs.python-requests.org/en/latest/index.html > > This page mentions both: > - underlying urllib3 (the line just before Testimonials) > - Thread Safety (last point in Featu

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-05-08 Thread kracethekingmaker
I don't want requests, to go into std lib at all and even kenneth doesn't if I am right. Vishal writes: http://docs.python-requests.org/en/latest/index.html This page mentions both: - underlying urllib3 (the line just before Testimonials) - Thread Safety (last point in Features) I am ** pred

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-05-08 Thread Noufal Ibrahim
Vishal writes: > http://docs.python-requests.org/en/latest/index.html > > This page mentions both: > - underlying urllib3 (the line just before Testimonials) > - Thread Safety (last point in Features) > > I am ** predicting ** that Requests will go into the std-lib very > soon :)) I'm not sure.

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-05-08 Thread Vishal
http://docs.python-requests.org/en/latest/index.html This page mentions both: - underlying urllib3 (the line just before Testimonials) - Thread Safety (last point in Features) I am ** predicting ** that Requests will go into the std-lib very soon :)) Enjoy, Vishal Sapre On Tue, May 8, 2012 at

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-05-07 Thread Baiju M
(Reply to an old thread) On Sat, Mar 3, 2012 at 10:47 AM, Baiju M wrote: > On Sat, Mar 3, 2012 at 10:07 AM, Gora Mohanty wrote: > > On 3 March 2012 09:41, Baiju M wrote: > > [...] > >> Sometimes features are very important. I stared using requests for one > >> work, but later I found that it

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-03-03 Thread Senthil Kumaran
On Sat, Mar 03, 2012 at 09:41:57AM +0530, Baiju M wrote: > On Sat, Mar 3, 2012 at 9:32 AM, Senthil Kumaran wrote: > > On Wed, Feb 29, 2012 at 08:21:31PM +, Anand Chitipothu wrote: > [...snip...] > >> I disagree. People look for simplicity. > > > > Yes, I agree that in general, people appreciat

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-03-02 Thread Baiju M
On Sat, Mar 3, 2012 at 10:07 AM, Gora Mohanty wrote: > On 3 March 2012 09:41, Baiju M wrote: > [...] >> Sometimes features are very important.  I stared using requests for one >> work, but later I found that it is not thread safe, then I switched to >> urllib3: >> http://urllib3.readthedocs.org/

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-03-02 Thread Gora Mohanty
On 3 March 2012 09:41, Baiju M wrote: [...] > Sometimes features are very important.  I stared using requests for one > work, but later I found that it is not thread safe, then I switched to > urllib3: > http://urllib3.readthedocs.org/en/latest/index.html Sorry, but I am confused. Is requests no

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-03-02 Thread Baiju M
On Sat, Mar 3, 2012 at 9:32 AM, Senthil Kumaran wrote: > On Wed, Feb 29, 2012 at 08:21:31PM +, Anand Chitipothu wrote: [...snip...] >> I disagree. People look for simplicity. > > Yes, I agree that in general, people appreciate simplicity. I too. > > My previous comment was more aligned with ho

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-03-02 Thread Senthil Kumaran
On Wed, Feb 29, 2012 at 08:21:31PM +, Anand Chitipothu wrote: > 2012/2/29 Senthil Kumaran : > > On Tue, Feb 28, 2012 at 03:17:53PM +0530, Anand Balachandran Pillai wrote: > >> For any kind of client side HTTP coding, I suggest the new requests > >> library. > >> I myself have been a heavy user

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-02-29 Thread Anand Chitipothu
2012/2/29 Senthil Kumaran : > On Tue, Feb 28, 2012 at 03:17:53PM +0530, Anand Balachandran Pillai wrote: >> For any kind of client side HTTP coding, I suggest the new requests library. >> I myself have been a heavy user of urllib2/urllib but these libraries are >> developer unfriendly and doesnt lo

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-02-29 Thread Senthil Kumaran
On Tue, Feb 28, 2012 at 03:17:53PM +0530, Anand Balachandran Pillai wrote: > For any kind of client side HTTP coding, I suggest the new requests library. > I myself have been a heavy user of urllib2/urllib but these libraries are > developer unfriendly and doesnt look like their problems are going

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-02-28 Thread Anand Balachandran Pillai
On Wed, Feb 22, 2012 at 3:34 PM, Amit Sethi wrote: > Hi all , Can someone explain to me why things are implemented the following > in urllib2. > > When I pass encoded url using http it again encodes the parameters > whereas in case of https it does not urlencode again > > so lets say the (http) ca

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-02-22 Thread Senthil Kumaran
On Wed, Feb 22, 2012 at 6:04 PM, Amit Sethi wrote: > When I pass encoded url using http it again encodes the parameters > whereas in case of https it does not urlencode again It should not happen this way. Both should behave the same for the url that you send.

Re: [BangPypers] Https and http difference in behaviour urllib2

2012-02-22 Thread Shekhar Tiwatne
On Wednesday 22 February 2012 03:34 PM, Amit Sethi wrote: Hi all , Can someone explain to me why things are implemented the following in urllib2. Show your code. It's then easier for people who are willing to help. When I pass encoded url using http it again encodes the parameters whereas in ca

[BangPypers] Https and http difference in behaviour urllib2

2012-02-22 Thread Amit Sethi
Hi all , Can someone explain to me why things are implemented the following in urllib2. When I pass encoded url using http it again encodes the parameters whereas in case of https it does not urlencode again so lets say the (http) call is http//:example.com?email=amit%40sethi.comthe request is h