Replies: 1 comment 2 replies
-
Thanks for the suggestion! This is intended to be solved via registries other than Microsoft/vcpkg (see #17161 and https://github.com/microsoft/vcpkg/blob/master/docs/specifications/registries-2.md). Because multiple minor versions of python cannot be built and installed side-by-side, it would require doubling our entire CI set to accommodate it. As you can imagine, this quickly gets out of hand as soon as you add 4 or 5 packages that require this treatment (32x the CI time). Therefore, we cannot properly support these variants in the public, curated catalog and instead encourage interested users to set up their own registries for these alternative versions. |
Beta Was this translation helpful? Give feedback.
-
I've recently discovered the "versions" feature of vcpkg and I think it is a great addition. The instructions on how to use this feature are posted here
Due to some limitations in the dependent libraries, I usually need to use python one major version older than the latest release, e.g. the latest version is 3.9.x as of today but I need to use python 3.8.x. I've checked the vcpkg versions file (https://github.com/microsoft/vcpkg/blob/master/versions/p-/python3.json) and I see that vcpkg supports up to python v3.8.3 for v3.8.x series. However, it seems like python released v3.8.9 a few weeks ago (https://www.python.org/downloads/).
Wouldn't be great for vcpkg to support v3.8 and v3.9 versions together? What do you think about it?
Beta Was this translation helpful? Give feedback.
All reactions