-
-
Notifications
You must be signed in to change notification settings - Fork 493
3.3.0 release #898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.3.0 release #898
Conversation
Replaced deprecated ruff config
Removing date from copyrights to ease maintenance is the practice nowadays, see https://aboutcode.org/2023/update-copyright-each-new-year/
Based on latest https://opensource.org/license/BSD-3-Clause, suggested removal of ambiguity from https://peps.python.org/pep-0639/appendix-mapping-classifiers/ and https://peps.python.org/pep-0639/#deprecate-license-classifiers Fixed #896
Put on hold until #899 is resolved. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
I have a test case that works fine with 3.2.2, but fails when using: git+https://github.com/oauthlib/oauthlib@dab6a5ae1830ddd8a79c1e9687f63508eae60b57 An assert starts failing here -- when refreshing the token: The failure is as follows:
So, with the new version an additional |
Might be related to changes added since 7e69a15 Based on the commit only, if |
Added similar behaviors to all interfaces where expires_at is parsed, this will facilitate the implementations. Note this is breaking change for those which are expecting the "default" `expires_at` (as in, not provided) to be a float. This will now default to a int.
Handle expires_at with best effort basis
Hi @pennersr, while the specification does not enforce having So the new behavior seems logical to me. Thanks for your feedback. |
Dear community, upstreams & downstream consumers @evonove, @masci, @singingwolfboy & al,
Please check if this 3.3.0 release is working with your projects.
Unless any major issues, this will go out soon,