Yes, it works. Thanks :-) --Regards, Denzil
On Mon, Jun 6, 2011 at 9:10 PM, Tom van der Woerdt <[email protected]> wrote: > In that case, try removing everything related to the req variable. Seems > it's all unrelated to the actual request (unless the oauth library is very > badly designed, of course). Line 22 all the way up to 35. > > Tom > > > On 6/6/11 5:38 PM, Correa Denzil wrote: >> >> Well, it turns out it's not the case. Both the points you mentioned >> weren't the issue as I see it. >> >> The issue was while I was creating the client I wasn't supplying the >> token. Check Line 20 in the gist. >> >> https://gist.github.com/1010430 >> >> --Regards, >> Denzil >> >> >> >> >> On Mon, Jun 6, 2011 at 8:58 PM, Correa Denzil<[email protected]> wrote: >>> >>> Tom : >>> >>> Are you sure? This gives me a : >>> >>> Traceback (most recent call last): >>> File "oauth_test.py", line 41, in<module> >>> resp, content = req.request(url, "GET") >>> AttributeError: 'Request' object has no attribute 'request' >>> >>> --Regards, >>> Denzil >>> >>> >>> >>> >>> On Mon, Jun 6, 2011 at 8:49 PM, Tom van der Woerdt<[email protected]> wrote: >>>> >>>> On 6/6/11 5:10 PM, Correa Denzil wro > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
