I apparently have a different vintage of httplib in my 2.6, since the raise CannotSendRequest() is on line 778.
It seems to mean reuse of an HTTPConnection object that isn't idle. Maybe a threading problem? Does this happen with the development server? pdb is your friend (standard advice). Bill On Mon, Sep 6, 2010 at 12:39 AM, ashy <ashwinmo...@gmail.com> wrote: > Hi All, > > Now I am getting 'Cannot send request' exception. > Exception Location: /usr/lib/python2.6/httplib.py in putrequest, line > 802 > Some problem with httplib. Any ideas? > > thanks > ashwin > > On Sep 4, 1:16 am, Bill Freeman <ke1g...@gmail.com> wrote: >> No. I'm not actually using twitter anywhere. I just remember the >> email saying that the API changed on Tuesday, so I'm not surprised if >> things that worked before are broken now. >> >> On Fri, Sep 3, 2010 at 10:26 AM, ashwin morey <ashwinmo...@gmail.com> wrote: >> > Hi Bill, >> >> > Did you try using django-twitter-oauth >> >http://github.com/henriklied/django-twitter-oauth#readme? >> > I got the error while using this app. >> >> > thanks >> > ashy >> >> > On Fri, Sep 3, 2010 at 7:46 PM, Bill Freeman <ke1g...@gmail.com> wrote: >> >> >> There was an email from twitter to it's users, yesterday or the day >> >> before, >> >> saying that they've changed their auth API. I think it was a change to >> >> requiring OAUTH, but you may want to check whether port or SSL changes >> >> have occurred. >> >> >> On Fri, Sep 3, 2010 at 10:08 AM, ashy <ashwinmo...@gmail.com> wrote: >> >> > Hi All, >> >> >> > I am using django-twitter-oauth app in my project, but I am getting >> >> > the following error while trying to connect to twitter.com. >> >> >> > Exception Value: (111, 'Connectionrefused') >> >> > Exception Location: /usr/lib/python2.6/socket.py in >> >> > create_connection, line 514 >> >> >> > token = get_unauthorised_request_token(CONSUMER,CONNECTION) >> >> > resp = fetch_response(oauth_request,connection) >> >> >connection.request(oauth_request.http_method, url) >> >> >> > Also, Iam working behind proxy. How can I use oauth library behind >> >> > proxy? Any ideas. >> >> >> > thanks >> >> > ashy >> >> >> > -- >> >> > You received this message because you are subscribed to the Google >> >> > Groups "Django users" group. >> >> > To post to this group, send email to django-us...@googlegroups.com. >> >> > To unsubscribe from this group, send email to >> >> > django-users+unsubscr...@googlegroups.com. >> >> > For more options, visit this group at >> >> >http://groups.google.com/group/django-users?hl=en. >> >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> >> "Django users" group. >> >> To post to this group, send email to django-us...@googlegroups.com. >> >> To unsubscribe from this group, send email to >> >> django-users+unsubscr...@googlegroups.com. >> >> For more options, visit this group at >> >>http://groups.google.com/group/django-users?hl=en. >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Django users" group. >> > To post to this group, send email to django-us...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > django-users+unsubscr...@googlegroups.com. >> > For more options, visit this group at >> >http://groups.google.com/group/django-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
