I've done some more digging into this but still can't figure out the problem. I thought perhaps the problem might be with the signature generation, but I wrote a little test to confirm that the same signature is being generated in Python2.5 and 2.6.
I updated fireeagle_api.py to use the oauth2 library (http:// github.com/simplegeo/python-oauth2) but I get exactly the same problem. The full response from the FireEagle server is: <rsp stat="fail"> <err code="23" msg="Invalid OAuth signature."/> </rsp> <!-- api3.bh.sp1.yahoo.net uncompressed/chunked Tue Apr 6 06:59:46 PDT 2010 --> What are the differences in python2.5/2.6 that might cause this problem? Thanks, Ben On Feb 21, 11:19 pm, Ben Dowling <[email protected]> wrote: > Hi, > > I'm using django-fireeagle (http://django-fireeagle.googlecode.com/svn/ > trunk/fire-eagle.html) on a project, which uses thePythonOAuth > module. WithPython2.6 everything works without any problems, but > withPython2.5I get the following error: > > Exception Type: FireEagleException > Exception Value: Invalid OAuth signature. (Code 23) > Exception Location: fireeagle_api.py in fetch_response, line 360 > > Can anybody help me get this working withPython2.5? > > Many thanks, > > Ben -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/oauth?hl=en.
