A new upstream version of Pygments is now available: 2.18.0.
This release includes updates for the wikitext lexer by @Diskdance:
Previously: T351744: New upstream release for Pygments (2.17.2)
A new upstream version of Pygments is now available: 2.18.0.
This release includes updates for the wikitext lexer by @Diskdance:
Previously: T351744: New upstream release for Pygments (2.17.2)
Change #1027245 had a related patch set uploaded (by BryanDavis; author: Bryan Davis):
[mediawiki/extensions/SyntaxHighlight_GeSHi@master] Update Pygments to 2.18.0
Change #1027251 had a related patch set uploaded (by BryanDavis; author: Bryan Davis):
[mediawiki/libs/Shellbox@master] syntaxhighlight: Update Pygments to 2.18.0
Pygments v2.18.0 requires Python 3.8+ as a runtime. The current test and default local development environments for MediaWiki are using Debian Buster containers which provide the EOL Python 3.7.3. Until these bump to a newer Debian distro with a newer Python version things are stuck. Debian Bookworm provides Python 3.11.2; Debian Bullseye provides Python 3.9.2.
I am not exactly sure what to mark this as blocked on. Maybe T319432: Migrate WMF production from PHP 7.4 to PHP 8.1? I think that fundamentally this blocked until we bump all the things past Buster to Bullseye or newer. That PHP 8.1 task looks like the same fundamental block.
Change #1032606 had a related patch set uploaded (by BryanDavis; author: Bryan Davis):
[mediawiki/extensions/SyntaxHighlight_GeSHi@master] Pygmentize: report stderr when exit code != 0 and stdout is empty
Change #1032606 merged by jenkins-bot:
[mediawiki/extensions/SyntaxHighlight_GeSHi@master] Pygmentize: report stderr when exit code != 0 and stdout is empty