Replies: 1 comment
-
As the pop-up window says, it's activated but your shell prompt didn't update. This usually happens if you activate a conda environment as part of your terminal startup (it's basically overwriting what we are doing). You can turn that off in your shell or opt out of activation entirely. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have multiple Python environments on my MacOS computer, including the built-in, brew, and conda.
I'd like the Terminal to automatically activate the environment I've selected whenever I open a new Terminal.
This functionality was working perfectly before the introduction of the new feature (#11039), even though it would always display
![截圖 2023-12-21 19 35 19](https://private-user-images.githubusercontent.com/48896687/292190387-66294c20-35bd-4ce6-85e2-ca89e60836fc.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMjIyNTksIm5iZiI6MTczOTMyMTk1OSwicGF0aCI6Ii80ODg5NjY4Ny8yOTIxOTAzODctNjYyOTRjMjAtMzViZC00Y2U2LTg1ZTItY2E4OWU2MDgzNmZjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDAwNTkxOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWZjZTMyMjk1MDU4YmEwOTAxNGM3YTkxOTdiOTg5ZGJhOTNmODQ1Nzc2NWE5MTE3NjkzYjZhZjcyN2IzYzNkNTcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.WtkSCpR-CNMRQiH5JCQ0Fto-4Pyy6zzK2qct2l3qAjg)
conda activate base
.For example, I select "test" env:
But now it use built-in Python:
![截圖 2023-12-21 19 37 52](https://private-user-images.githubusercontent.com/48896687/292191688-72de57b7-9334-4c6e-917d-d7be04c58f8e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMjIyNTksIm5iZiI6MTczOTMyMTk1OSwicGF0aCI6Ii80ODg5NjY4Ny8yOTIxOTE2ODgtNzJkZTU3YjctOTMzNC00YzZlLTkxN2QtZDdiZTA0YzU4ZjhlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDAwNTkxOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTlhNWIyY2IwMTM2ZTE3MjllMmY5Y2E5MzU5YzE2Y2M2MzcyOWU1YTM3NjYzMGI0MjIxYjk5YjhhYmNjNGMwZTAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0._wI4QYtDx6fyaFptqgFLQsVYukmUulK4ngYZ0ksKYPQ)
environment contributions
extension log
vsode setting
conda setting
I have temporarily add
pythonTerminalEnvVarActivation
topython.experiments.optOutFrom
in settings to make it work properly. I'm curious if there's a more optimal solution to resolve this issue. Any suggestions?Beta Was this translation helpful? Give feedback.
All reactions