-
-
Notifications
You must be signed in to change notification settings - Fork 491
Release 2.0.7 #519
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
Release 2.0.7 #519
Conversation
The wheel package format supports including the license file. This is done using the [metadata] section in the setup.cfg file. For additional information on this feature, see: https://wheel.readthedocs.io/en/stable/index.html#including-the-license-in-the-generated-wheel-file (cherry picked from commit 1421524)
…thlib#496) For Travis CI documentation on including a bdist_wheel distribution, see: https://docs.travis-ci.com/user/deployment/pypi/#Uploading-different-distributions Fixes oauthlib#493 (cherry picked from commit 4b85d90)
* Check access token in self.token dict * fix typo (cherry picked from commit fa0b63c)
(cherry picked from commit 66d7296)
* Added sphinx build for developers Rationale is to build docs locally to prevent RTD to break later. * Replace manual sphinx into make * Renamed idan URL to oauthlib community * Renamed http into https URLs since http is returning 302 * python requests library renamed its home URL * Add ignore list for "make linkcheck" linkcheck is doing requests to github with anonymous access, however creating an issue require an logged-in account * virtualenv changed its homepage and website. * Fixed broken link (cherry picked from commit 32e5ad1)
(cherry picked from commit 3d24818)
(cherry picked from commit d93403a)
LGTM |
👍 |
Yes, I've run the test suites for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Do we have blockers still? I think this PR can be accepted safely (into 2.x branch) and also #521 #523 #520 #522 #518 into master. Those are around build/docs tooling, they might be needed before tagging the branch 2.x into 2.0.7. Will be great if someone could cope with these PR, @thedrow ? any other with write permissions ? |
Hm, which one(s) you'd consider new features specifically @thedrow? |
Here's a milestone for this release... |
This cherry picks the PRs mentioned in the changelog into the 2.x branch.
Following semantic versioning, not included are:
client_id
in web request body (Fix client_id in web request body #505) (not sure if backward compatible, for 3.0.0)