Will the default warning behavior for scope changes be updated?

[mahima-desetty]

I’m aware of the current avenues to get past the warning raised in parameters.py (via signals, OAUTHLIB_RELAX_TOKEN_SCOPE env var, reading the token parameter on the warning raised), but I’m wondering if there are any plans to change the way the warning behaves when there is a scope change if none of the workarounds are implemented. Right now, if there is a scope change and users have not already handled this scenario, it could break their applications.

From https://github.com/oauthlib/oauthlib/pull/276#issuecomment-60288949…
“Still have the warning enabled by default. Can be disabled with OAUTHLIB_RELAX_TOKEN_SCOPE. signals will be sent in either case.

We can think about changing this default going into 1.0.”

[auvipy]

do you have the bandwidth to come with a draft PR with what change you are suggesting, please?