Repository navigation
Test that UI indicates terminal activation when activating using environment variables #21298
Description
Activity
- locked as resolved and limited conversation to collaborators
on Jun 26, 2023 - changed the title
[-]Test multiroot support for terminal activation using environment variables[/-][+]Test terminal prompt for multiroot workspace when in `pythonTerminalEnvVarActivation` experiment[/+]on Aug 14, 2023 - changed the title
[-]Test terminal prompt for multiroot workspace when in `pythonTerminalEnvVarActivation` experiment[/-][+]Test terminal prompt when activating terminals using environment variables[/+]on Aug 14, 2023 - changed the title
[-]Test terminal prompt when activating terminals using environment variables[/-][+]Test that UI indicates terminal activation when activating using environment variables[/+]on Aug 14, 2023 4 remaining items
mine always says
(base) PS C:\Users\eleanorboyd\testFilesWindows\conda-shell>is it ok that it says base and not .venv?Yes you can ignore that for now. Please run the Python command specified to see which environment is actually activated.
This isn't working for me at all:
Me and Aaron discussed here that it actually works: #21887 (comment), but it was the same confusion that Eleanor Boyd (@eleanorjboyd) has, which is that it always shows
(base)regardless of which env is actually activated.Sorry for the trouble.
Is it standard for Python docs to be in a GH wiki. I'm wondering if this should be on the VS Code website so we can track things like page views?
Logan Ramos (@lramos15) We have plans to move it there, but right now this is behind an experiment hence isn't applicable for everyone.
- unlocked this conversation
on Aug 29, 2023 
Logan Ramos (@lramos15) Were you able to test for
zshandfishon Linux?
Logan Ramos (@lramos15) Were you able to test for
zshandfishon Linux?Oh I do not have those installed, do I need to install them for the TPI. I got confused by the wording
please tick whatever is available in your OSwhich made me think it was test what you have.Sorry, if you could install them that would be great. Our codespaces already has it pre-installed so you can also use that, thanks!
Sorry, if you could install them that would be great. Our codespaces already has it pre-installed so you can also use that, thanks!
Done 👍
Reacted by Kartik Raj- locked as resolved and limited conversation to collaborators
on Sep 29, 2023
Refs: #21793
Complexity: 5
Create Issue
Requirements
Similar to #21102 hence preassigning.
python -m venv <name>to create virtual envs.PATHduring installation.conda init --all& restart the shell.conda create -n <name> python -y.Verification
Run
conda config --set auto_activate_base True.Open a workspace folder and activate Python extension by opening a Python file.
Select a virtual environment using
Python: Select Interpretercommand.Loop -> Do the following for all terminal shell types:
(base): Active venv is activated in terminal but terminal indicates that(base)is activated #21887):.venvcreated viapython -m venv .venvit looks something like:Terminal: Select Default Profile, saybash->fishSelect a conda environment using
Python: Select Interpretercommand and repeat the above loop.If the notification was visible at some point: