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:

>
> New submission from Ned Deily:
>
> [..]/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
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue30939>
> _______________________________________
>