-
-
Notifications
You must be signed in to change notification settings - Fork 34.8k
gh-153227: Use a development version of Pygments #153228
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
hugovk
merged 4 commits into
python:main
from
ZeroIntensity:docs/use-development-pygments
Jul 7, 2026
+21
−17
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We did need to manually remove this line to workaround a
packagingbug, but I think that might be fixed now. Let's leave this here and find out.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It failed in the CI the last time IIRC, right? In that case it's passing now!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the details are in #149058.
pypa/packaging#1178 was fixed in pypa/packaging#1179 but not actually released yet.
What fixed it is python/release-tools#394 changing our dev version from
3.15.0b1+to3.15.0b1+devto comply with PEP 440.That's only been applied to 3.15+, so 3.14 and older will need to keep
requires-pythonuntil the next packaging release (and perhaps pip to vendor it).We could also consider applying python/release-tools#394 to 3.14 and older.
Anyway, we only have this
pylock.tomlin 3.15+, and only need this pygmentslazyfix for 3.15+, so we're all good :)