this shouldn't be compiled against a vcredist that requires copying and pasting dlls into the python installation

[doctorpangloss]

Describe the bug

Environment details

[woct0rdho]

A binary built with a given version of MSVC is only guaranteed to run with a vcredist of the same or newer version. AFAICT the 'proper' way to manage the vcredist version is to let the user install one and only vcredist on their computer (apart from the old vcredists before 2015, which are different from the modern vcredist we talk about), and let Windows Update keep it up to date. Unfortunately, a lot of programs still bundle their own vcredist, including Python.

Currently I'm using the default MSVC version on GitHub Actions Windows runner, and the LLVM built by the official Triton team, which is built on the same runner (see the workflow for details).

PyTorch requires MSVC 2019 before PyTorch 2.8, and MSVC 2022 since PyTorch 2.8 . LLVM is moving fast and requires a recent version of MSVC, but I guess it will be more stable when LLVM 20 LTS is there.

A few months ago (before ComfyUI users upgraded to a recent version of Python 3.12.x) I've seen a lot of complaint that the vcredist bundled in the embedded Python (or somewhere else on the user's computer) is too old, but nowadays these complaints are much fewer. It's possible that we build with an older MSVC if really needed. Can you suggest what MSVC version would be more suitable?