[issue36853] inconsistencies in docs builds (Sphinx 2)

Jason R. Coombs added the comment: New changeset ebe709dc1d7c1f9f07dc7d77e53674d2500b223e by Jason R. Coombs (Anthony Sottile) in branch '3.7': bpo-36853: Fix suspicious.py to actually print the unused rules (#13579) (#15653)

[issue36853] inconsistencies in docs builds (Sphinx 2)

Change by Anthony Sottile : -- pull_requests: +15320 pull_request: https://github.com/python/cpython/pull/15653 ___ Python tracker ___

[issue36853] inconsistencies in docs builds (Sphinx 2)

Jason R. Coombs added the comment: New changeset b365cfae4675ae90df329cb1179a5664e8283c13 by Jason R. Coombs (Miss Islington (bot)) in branch '3.8': bpo-36853: Fix suspicious.py to actually print the unused rules (GH-13579) (GH-15649)

[issue36853] inconsistencies in docs builds (Sphinx 2)

Change by miss-islington : -- pull_requests: +15316 pull_request: https://github.com/python/cpython/pull/15649 ___ Python tracker ___

[issue36853] inconsistencies in docs builds (Sphinx 2)

Jason R. Coombs added the comment: New changeset e1786b54162e2bfb01ca5aafa19d596c4af5a803 by Jason R. Coombs (Anthony Sottile) in branch 'master': bpo-36853: Fix suspicious.py to actually print the unused rules (#13579)

[issue36853] inconsistencies in docs builds (Sphinx 2)

David Jones added the comment: I believe the issue is only triggered if you actually have some suspicious markup in your documentation (which is why your plain build on Sphinx 2 appears to work). Remove some lines from Doc/tools/susp-ignored.csv to trigger it. -- nosy: +drj

[issue36853] inconsistencies in docs builds (Sphinx 2)

Change by Anthony Sottile : -- nosy: +Anthony Sottile ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36853] inconsistencies in docs builds (Sphinx 2)

Change by Anthony Sottile : -- keywords: +patch pull_requests: +13799 stage: -> patch review pull_request: https://github.com/python/cpython/pull/13579 ___ Python tracker ___

[issue36853] inconsistencies in docs builds (Sphinx 2)

Jason R. Coombs added the comment: > I've just locally ran sphinx 2.0.0 on 071cbd4ea1 (the current tip of your PR) > and I'm not getting any error, which one are you getting? The issue occurs on 2347d3ae36 with `make suspicious` with Sphinx 2.0.0 and 2.0.1. ``` Doc 2347d3ae36 $ make

[issue36853] inconsistencies in docs builds (Sphinx 2)

Karthikeyan Singaravelan added the comment: See also https://github.com/python/cpython/pull/13579 that replaces self.warn with self.logger.warn in Doc/tools/extensions/suspicious.py -- nosy: +xtreak ___ Python tracker

[issue36853] inconsistencies in docs builds (Sphinx 2)

Change by Matthias Bussonnier : -- nosy: +mbussonn ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36853] inconsistencies in docs builds (Sphinx 2)

SilentGhost added the comment: > Second, we should probably determine why the doc builds are failing on Sphinx > 2 and update the `suspicious` code to support Sphinx 2. They're failing because in sphinx 2 old and deprecated (since 1.6) custom logging API was removed. So all Builder.warn

[issue36853] inconsistencies in docs builds (Sphinx 2)

Julien Palard added the comment: Hi Jaraco, We're using sphinx 1.8 in production (docs.python.org) but we're ready for sphinx 2 so we should upgrade, and when we'll upgrade, we'll upgrade it everywhere. You're right, `make venv` does not specify a version, at the sphinx 2 bump we'll have

[issue36853] inconsistencies in docs builds (Sphinx 2)

Change by Ned Deily : -- nosy: +mdk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36853] inconsistencies in docs builds (Sphinx 2)

New submission from Jason R. Coombs : In working on some docs contributions, I've run into issues where docs builds are failing in CI differently than they're failing locally. Locally, running `make venv` from `Docs/` results in Sphinx 2, whereas on Azure Pipelines, the docs are built with