Skip to content

[3.10] gh-114021: Pin various sphinxcontrib extensions to older versions (GH-114022) #114038

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

Merged
merged 1 commit into from
Jan 17, 2024

Conversation

AA-Turner
Copy link
Member

@AA-Turner AA-Turner commented Jan 13, 2024

…o older versions (pythonGH-114022).

(cherry picked from commit 94b1d1f)

Co-authored-by: Ronald Oussoren <ronaldoussoren@mac.com>
@m-aciek
Copy link
Contributor

m-aciek commented Jan 13, 2024

We are introducing constraints.txt, I am wondering if we shouldn't convert current pins in requirements.txt of transitive dependencies to constraints.

# Docutils version is pinned to a version compatible with Sphinx
# version <3.5.4. It can be removed after bumping Sphinx version to at
# least 3.5.4.
docutils==0.17.1
# Jinja version is pinned to a version compatible with Sphinx version <4.5.
jinja2==3.0.3

into

# docutils 1.18 is incompatible with Sphinx <3.5.4
docutils<1.18
# jinja2 3.1.0 is incompatible with Sphinx <4.5
jinja2<3.1.0

in constraints.txt for consistency.

@AA-Turner
Copy link
Member Author

This is a backport, minimal changes are preferable.

@ambv ambv merged commit 6661b22 into python:3.10 Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants