-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
fix pydoc-topics to work with Sphinx 1.7 #6475
Conversation
In fact, we now require a newer Sphinx version because APIs have moved around.
Thanks @benjaminp for the PR 🌮🎉.. I'm working now to backport this PR to: 2.7, 3.6, 3.7. |
In fact, we now require a newer Sphinx version because APIs have moved around. (cherry picked from commit acfb087) Co-authored-by: Benjamin Peterson <benjamin@python.org>
GH-6500 is a backport of this pull request to the 3.7 branch. |
Sorry, @benjaminp, I could not cleanly backport this to |
In fact, we now require a newer Sphinx version because APIs have moved around. (cherry picked from commit acfb087) Co-authored-by: Benjamin Peterson <benjamin@python.org>
GH-6501 is a backport of this pull request to the 3.6 branch. |
In fact, we now require a newer Sphinx version because APIs have moved around.. (cherry picked from commit acfb087) Co-authored-by: Benjamin Peterson <benjamin@python.org>
GH-6502 is a backport of this pull request to the 2.7 branch. |
In fact, we now require a newer Sphinx version because APIs have moved around. (cherry picked from commit acfb087) Co-authored-by: Benjamin Peterson <benjamin@python.org>
In fact, we now require a newer Sphinx version because APIs have moved around. (cherry picked from commit acfb087) Co-authored-by: Benjamin Peterson <benjamin@python.org>
In fact, we now require a newer Sphinx version because APIs have moved around.