Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Use conda run to get the activated environment variables instead of activation using shell scripts #18748

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

Merged
merged 5 commits into from
Mar 22, 2022

Conversation

karrtikr
Copy link

Closes #18698

@karrtikr karrtikr added the skip tests Updates to tests unnecessary label Mar 22, 2022
@karrtikr karrtikr removed the skip tests Updates to tests unnecessary label Mar 22, 2022
@karrtikr karrtikr merged commit ae9314f into microsoft:main Mar 22, 2022
@karrtikr karrtikr deleted the condarunenvironment branch March 22, 2022 13:59
wesm pushed a commit to posit-dev/positron that referenced this pull request Mar 28, 2024
… activation using shell scripts (microsoft/vscode-python#18748)

* Use `conda run` to get the activated environment variables instead of activation using shell scripts

* news

* Have larger timeout for conda

* Doc comment

* Fix tests
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 this pull request may close these issues.

Use conda run to get the activated environment variables instead of activation using shell scripts
1 participant