Python dependencies not packaged inside the minted MiKTeX package

[filips123]

Based on the documentation, minted v3 bundles all Python dependencies inside the package, so no manual installation (apart from Python itself) is necessary:

As of minted version 3, all Python software including Pygments is bundled with the LATEX package when it is installed with a TEX package manager, and no dependencies must be installed separately.

When the minted package is installed, it includes the latexminted Python executable and all required Python libraries including Pygments. For these to function correctly, Python 3.8+ must be installed and on PATH when the latexminted executable runs.

However, installing minted using MiKTeX on Windows does not install latexminted and other Python dependencies, so syntax highlighting fails:

Package minted Error: Cannot highlight code (minted executable is unavailable or disabled); attempting to typeset without highlighting.

According to MiKTeX/miktex#1538 (which as been closed due to inactivity), the minted package does not include include the necessary Python scripts. I can also confirm they are not present in my MiKTeX installation:

tex\generic\tex4ht\minted-sty-hooks.4ht
tex\generic\tex4ht\minted.4ht
tex\latex\minted\
tex\latex\minted\minted.sty
tex\latex\minted\minted1.sty
tex\latex\minted\minted2.sty
tex\latex\tcolorbox\tcbminted.code.tex
tpm\packages\minted.tpm

I also tried to install the minted__source which includes the Python scripts, but they are stored in a different directory, so the compilation still doesn't work.

Can the necessary scripts and dependencies be bundled inside the minted package, so the compilation works without any additional setup?

[gpoore]

The minted package includes all Python dependencies. TeX Live (with CTAN) bundles minted correctly, and requires no additional setup. MiKTeX has never bundled minted v3 correctly (files are omitted). As far as I know, the linked MiKTeX issue was closed automatically without any attempt to rebundle minted. I should update the documentation to say that MiKTeX provides an incomplete installation, and then you need to install the latexminted executable from PyPI or elsewhere.

There should be no technical issues for MiKTeX; TeX Live has correctly bundled minted v3 from the beginning. If you want this fixed, I'd suggest opening another MiKTeX issue. There isn't anything I can do from my end.

[filips123]

I've reported the issue to MiKTeX (MiKTeX/miktex-packaging#494) and they've added Python dependencies to the package. There are now the following minted files in the MiKTeX installation:

miktex\bin\x64\latexminted.exe
scripts\minted\
scripts\minted\latexminted-0.6.0-py3-none-any.whl
scripts\minted\latexminted.py
tex\generic\tex4ht\minted-sty-hooks.4ht
tex\generic\tex4ht\minted.4ht
tex\latex\minted\
tex\latex\minted\minted.sty
tex\latex\minted\minted1.sty
tex\latex\minted\minted2.sty
tex\latex\tcolorbox\tcbminted.code.tex
tpm\packages\minted.tpm

Compiling with latexmk main.tex -pdf -enable-write18 now works fine.

Also, I've seen that in TeX Live, it's no longer necessary to allow arbitrary shell commands, as latexminted is now a trusted executable. Is it possible to do the same for MikTeX (so users don't need to manually edit configuration)? Should this also be reported to MiKTeX maintainers?

Also, the error message says that some problems may be caused when MiKTeX is being used with -aux-directory or -output-directory without setting a TEXMF_OUTPUT_DIRECTORY environment variable. Is this also something that could be fixed by default in the MiKTeX package/configuration?

[muzimuzhi]

Is it possible to do the same for MikTeX (so users don't need to manually edit configuration)? Should this also be reported to MiKTeX maintainers?

Yes and yes. I added MiKTeX/miktex-packaging#494 (comment).

[filips123]

Thanks! Is there also something that should be configured to make TEXMF_OUTPUT_DIRECTORY not necessary when using a custom output/auxiliary directory?

[muzimuzhi]

According to the latest doc for package option cachedir,

Note that the cache directory is relative to -output-directory or equivalently the
TEXMF_OUTPUT_DIRECTORY environment variable, if that is set.

I just checked the behavior in TeX Live, using a BasicTeX 2025 installed on macOS. And it does respect both -output-directory and TEXMF_OUTPUT_DIRECTORY.