compliance fixes

[joerussbowman]

Would it be possible to move the compliance fixes up from requests-oauthlib up to oauthlib in order for more oauthlib projects to take advantage of them?

[ib-lundgren]

Looking at the small selection we have here we certainly could. I added them here because I thought there would be much wider discrepancies and wanted to keep the "dirt" out of oauthlib.

I think a fairly naive "automatic fixing of common errors" compatibility mode could be added to the oauthlib clients, possibly off by default.

Fancy digging into this?

[joerussbowman]

Maybe, I'm currently working on an oauthlib implementation for tornado. I'm focusing on the providers first. Let me take a look at this when I get to working on clients. The plan is for the project I'm working on to replace the current auth module included with tornado. That supports some of the providers you have tweaks for so it is a bridge I will be crossing.

[ib-lundgren]

Sounds good.

Will ping you here in case I get around to it myself :)

On Wed, Jul 9, 2014 at 3:06 AM, Joseph Bowman [email protected]
wrote:

Maybe, I'm currently working on an oauthlib implementation for tornado.
I'm focusing on the providers first. Let me take a look at this when I get
to working on clients. The plan is for the project I'm working on to
replace the current auth module included with tornado. That supports some
of the providers you have tweaks for so it is a bridge I will be crossing.

—
Reply to this email directly or view it on GitHub
#131 (comment)
.

[ib-lundgren]

With the exception on LinkedIn all fixes are now in oauthlib master thanks to oauthlib/oauthlib#268.