You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Sphinx 1.6.3 deprecation warning for sphinx.util.compat.Directive in docs builds #75122
[..]/sphinx/util/compat.py:40: RemovedInSphinx17Warning: sphinx.util.compat.Directive is deprecated and will be removed in Sphinx 1.7, please use docutils' instead.
RemovedInSphinx17Warning)
The solution is to import Directive directly from docutils. PR to follow for master, needs to be cherrypicked to all maintenance branches and, ideally, all current security-only branches.
I wonder if we should pin sphinx directly instead of the approximate pin we
have now to prevent this sort of thing in the future? I had figured they
wouldn't introduce a new warning in a bugfix release but I was wrong in
that assumption.
[..]/sphinx/util/compat.py:40: RemovedInSphinx17Warning:
sphinx.util.compat.Directive is deprecated and will be removed in Sphinx
1.7, please use docutils' instead.
RemovedInSphinx17Warning)
The solution is to import Directive directly from docutils. PR to follow
for master, needs to be cherrypicked to all maintenance branches and,
ideally, all current security-only branches.
----------
assignee: docs@python
components: Documentation
messages: 298401
nosy: brett.cannon, docs@python, larry, ned.deily
priority: normal
severity: normal
stage: patch review
status: open
title: Sphinx 1.6.3 deprecation warning for sphinx.util.compat.Directive
in docs builds
versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6,
Python 3.7
I wonder if we should pin sphinx directly instead of the approximate pin we
have now to prevent this sort of thing in the future?
Perhaps. OTOH, we will find out about Sphinx incompatibilities pretty quickly that way, rather than having doc builds potentially silently fail or only finding out about the problem at release time.
Activity
ned-deily commentedon Jul 15, 2017
[..]/sphinx/util/compat.py:40: RemovedInSphinx17Warning: sphinx.util.compat.Directive is deprecated and will be removed in Sphinx 1.7, please use docutils' instead.
RemovedInSphinx17Warning)
The solution is to import Directive directly from docutils. PR to follow for master, needs to be cherrypicked to all maintenance branches and, ideally, all current security-only branches.
ned-deily commentedon Jul 15, 2017
New changeset 50f5816 by Ned Deily in branch 'master':
bpo-30939: Avoid Sphinx deprecation warning in docs build. (bpo-2721)
50f5816
ned-deily commentedon Jul 15, 2017
New changeset bbd0f42 by Ned Deily in branch '3.6':
bpo-30939: Avoid Sphinx deprecation warning in docs build. (bpo-2721) (bpo-2722)
bbd0f42
ned-deily commentedon Jul 15, 2017
New changeset ada3f31 by Ned Deily in branch '3.5':
bpo-30939: Avoid Sphinx deprecation warning in docs build. (bpo-2721) (bpo-2723)
ada3f31
ned-deily commentedon Jul 16, 2017
New changeset 64a9f3d by Ned Deily in branch '2.7':
bpo-30939: Avoid Sphinx deprecation warning in docs build. (bpo-2721) (bpo-2725)
64a9f3d
brettcannon commentedon Jul 16, 2017
I wonder if we should pin sphinx directly instead of the approximate pin we
have now to prevent this sort of thing in the future? I had figured they
wouldn't introduce a new warning in a bugfix release but I was wrong in
that assumption.
On Sat, Jul 15, 2017, 12:19 Ned Deily, <report@bugs.python.org> wrote:
ned-deily commentedon Jul 17, 2017
Perhaps. OTOH, we will find out about Sphinx incompatibilities pretty quickly that way, rather than having doc builds potentially silently fail or only finding out about the problem at release time.
larryhastings commentedon Jul 22, 2017
New changeset 3b3a5a5 by larryhastings (Ned Deily) in branch '3.4':
bpo-30939: Avoid Sphinx deprecation warning in docs build. (bpo-2721) (bpo-2724)
3b3a5a5