gh-153227: Use a development version of Pygments#153228
Open
ZeroIntensity wants to merge 1 commit into
Open
Conversation
ZeroIntensity
requested review from
AA-Turner,
StanFromIreland and
hugovk
as code owners
ZeroIntensity
added
the
needs backport to 3.15
Member
Author
|
@hugovk Any advice on the CI failure here? I don't think |
Member
|
Perhaps if we use the archive instead of VCS? |
hugovk
reviewed
Jul 6, 2026
Comment on lines
6
to
11
| # The Sphinx version is pinned so that new versions that introduce new warnings | ||
| # won't suddenly cause build failures. Updating the version is fine as long | ||
| # as no warnings are raised by doing so. | ||
| # Keep this version in sync with ``Doc/conf.py``. | ||
| pygments @ git+https://github.com/pygments/pygments@2cad2642058441b59782a6a18f03c98c42d081f1 | ||
| sphinx<9.0.0 |
Member
There was a problem hiding this comment.
This comment block applies to Sphinx, so move the pygments line further down.
And let's add a comment, something like:
# Temporary direct requirement,
# pending release of Pygments > 2.20.0
# https://github.com/pygments/pygments/discussions/3145
pygments @ etc
| # uv pip compile requirements.txt --exclude-newer P14D --exclude-newer-package linklint=PT0S --exclude-newer-package python-docs-theme=PT0S --no-cache --output-file Doc/pylock.toml --python-version 3.12 --universal | ||
| lock-version = "1.0" | ||
| created-by = "uv" | ||
| requires-python = ">=3.12" |
Member
There was a problem hiding this comment.
We did need to manually remove this line to workaround a packaging bug, but I think that might be fixed now. Let's leave this here and find out.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
uv decided to upgrade other dependencies in
pylock.toml; I didn't see any failures, so I decided to leave it.lazy importis not highlighted in the docs #153227