{{ message }}
[3.4] bpo-30939: Avoid Sphinx deprecation warning in docs build. (#2721)#2724
Merged
larryhastings merged 2 commits intoJul 22, 2017
Merged
[3.4] bpo-30939: Avoid Sphinx deprecation warning in docs build. (#2721)#2724larryhastings merged 2 commits into
larryhastings merged 2 commits into
Conversation
Member
Sorry, something went wrong.
(cherry picked from commit 50f5816)
|
@ned-deily, thanks for your PR! By analyzing the history of the files in this pull request, we identified @loewis, @birkenfeld and @benjaminp to be potential reviewers. |
Sorry, something went wrong.
Member
Author
|
@larryhastings I'll let you decide if you want to take this for 3.4 or not. |
Sorry, something went wrong.
Contributor
|
Yeah, this one's for me. |
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.
(cherry picked from commit 50f5816)
https://bugs.python.org/issue30939