[issue47138] Bump Sphinx or pin Jinja2 to fix docs build

[Hugo van Kemenade]

Change by Hugo van Kemenade :


--
pull_requests: +30234
pull_request: https://github.com/python/cpython/pull/32153

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue47138] Bump Sphinx or pin Jinja2 to fix docs build

[Hugo van Kemenade]

Change by Hugo van Kemenade :


--
pull_requests: +30235
pull_request: https://github.com/python/cpython/pull/32154

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue47138] Bump Sphinx or pin Jinja2 to fix docs build

[Ned Deily]

Ned Deily  added the comment:

Thank you both for addressing this. The main reason for minimizing changes to 
the docs build chain for brances in bugfix or security-fix-only phases is that 
many distributors of Python also release the Python docs as a package and they 
do not necessarily rely on using our fairly-recent venv step in the Docs 
Makefile. In particular, they want to use the versions of Sphinx et al that 
they release as packages. If we change the required versions for these 
mid-stream, they not only have to update the docs themselves but have to go 
through the process of updating the other packages (like Sphinx) which may have 
other consequences. This can also impact our own on-line doc building process. 
(Version updates for a new Python feature release prior to its entering beta 
phase are not a problem.) So it is best to do the minimal amount of version 
updating for releases in the field, preferably none (as in pinning existing 
versions). In that spirit, we should also just pin the Jinja2 version for 3.10
  and 3.9.

--
nosy: +ned.deily

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue47138] Bump Sphinx or pin Jinja2 to fix docs build

[Maciej Olko]

Maciej Olko  added the comment:

I've update both PRs to contain the pin only.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue47138] Bump Sphinx or pin Jinja2 to fix docs build

[Maciej Olko]

Change by Maciej Olko :


--
pull_requests: +30232
pull_request: https://github.com/python/cpython/pull/32109

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue47138] Bump Sphinx or pin Jinja2 to fix docs build

[Maciej Olko]

Change by Maciej Olko :


--
keywords: +patch
nosy: +Maciej Olko
nosy_count: 2.0 -> 3.0
pull_requests: +30231
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/32111

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue47138] Bump Sphinx or pin Jinja2 to fix docs build

[Hugo van Kemenade]

Hugo van Kemenade  added the comment:

re: https://bugs.python.org/issue45618#msg416017

Maciej Olko, please could you update these PRs to keep the Sphinx version the 
same and only pin Jinja2 to match?

3.7: https://github.com/python/cpython/pull/32109
3.8: https://github.com/python/cpython/pull/32111

I guess update them to use this bpo too. Thanks!

--
title: Bump Sphinx to fix docs build -> Bump Sphinx or pin Jinja2 to fix docs 
build

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com