Skip to content
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

Timeline for dropping vs2017 #71

Closed
16 of 17 tasks
h-vetinari opened this issue Dec 14, 2023 · 1 comment · Fixed by #80
Closed
16 of 17 tasks

Timeline for dropping vs2017 #71

h-vetinari opened this issue Dec 14, 2023 · 1 comment · Fixed by #80

Comments

@h-vetinari
Copy link
Member

h-vetinari commented Dec 14, 2023

We bumped the default windows compilers across conda-forge to vs2019 over a year ago (conda-forge/conda-forge-pinning-feedstock#3167), and usage of the previous vs2017 toolchain has dwindled.

Based on the following searches (in conda_build_config.yaml resp. meta.yaml), the only remaining feedstocks using vs2017 are as follows (I'm noting in brackets where the pin is set):

In particular, everything that added pins on vs2017 before August 2022 was "just" selecting the default compilers.

Comatose / dead feedstocks

@h-vetinari
Copy link
Member Author

Apparently MSFT removed the vc141 components (see #78), so I think this might have been decided for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant