We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We should setup our nightly tests to use conda. This has a number of benefits:
It looks like Azure DevOps has built in support for miniconda, as I think we only need to follow directions here: https://docs.microsoft.com/en-us/azure/devops/pipelines/ecosystems/anaconda?view=azure-devops&tabs=macos#add-conda-to-your-system-path
The text was updated successfully, but these errors were encountered:
This would also allow us to test this bug here (once I submit the fix for it): microsoft/vscode-python#3123
Sorry, something went wrong.
Test that we can re-enable when this is fixed: 'Multiple Interpreters' in interactiveWindow.functional.
This should also create a test for switching kernels (not just environments).
Can see conda doing it's thang in the functional flake pipeline, validated.
IanMatthewHuff
rchiodo
No branches or pull requests
We should setup our nightly tests to use conda. This has a number of benefits:
It looks like Azure DevOps has built in support for miniconda, as I think we only need to follow directions here:
https://docs.microsoft.com/en-us/azure/devops/pipelines/ecosystems/anaconda?view=azure-devops&tabs=macos#add-conda-to-your-system-path
The text was updated successfully, but these errors were encountered: