Closed sampsyo closed 9 years ago
Yikes, yeah this is definitely an issue. Replacing python-oauth2 won't be a quick task, but I agree that it must be done at some point. Thanks for the suggestions; I'll investigate this a bit more.
Cheers, Rodney
Cool! I'm happy to help if I can (maybe I'll get around to throwing together an rauth patch for your consideration, for example).
Also, did you mean to close this issue? I know I often hit the wrong button under the comment box. :smiley:
That would be awesome! And no, I'll reopen it. haha
Hello there ! I'm looking forward to using the discogs client. Any news on this issue ?
Thanks
@vindarel We've just released a bug fix that should resolve this issue. Please take a look and let us know if you have further issues.
Thanks!
Great news ! I'll tell you as soon as I test it.
Searching for a non-ASCII term causes this error:
This is due to a known bug in python-oauth2: https://github.com/simplegeo/python-oauth2/issues/154. That library, unfortunately, appears to be abandoned: the last commit was in 2011 (c.f. this lament over the sorry state of Python OAuth libraries).
It's worth noting that this was not an issue when sending non-ASCII requests without OAuth authentication because they don't go through the broken library. This has only come up recently because the search API now requires authentication, so we're now these previously-working requests are now hitting this bug.
As unattractive as it seems, I think the only solution may be to move to a more modern OAuth library. Personally, I've had success with rauth.