-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
environment duplication -- interference with conda init #22233
Comments
@dataders Thanks for reaching out, the behavior is actually the similar to what conda does: If you notice at the To fix the UI you can run the following command:
and restart the shell. But things should already work as is. We plan to improve the UI to just show |
@karrtikr thanks for the helpful response! I can see the light at the end of tunnel y'all are in for improved UX for Python environment management in VSCode. I had gotten so used to the manual env activation post shell launch, but now with your provided extra conda config, I can see a brave new world! I've added the config you mentioned (dataders/dotfiles@71db253), but am I correct in understanding that in a future release, it won't be needed anymore? Still trying to wrap my head around future happy path for env management -- though would be more than happy to contrib to user docs on this once #22128 is shipped. |
p.s. as someone who works with Python and VSCode everyday your work is very much appreciated. Especially because you and the vscode-python team double down on contributing to not just this extension, but outside of your project to effectively the entire Python ecosystem. To me that's the real magic going on here. Here's hoping for the next generation of Python devs not having to go as deep into environment and package management as we find ourselves today. Cheers! |
Thanks for your kind words! Here's what we've currently planned for the docs: microsoft/vscode-docs#6590, your willingness to help improve it is much appreciated.
That's right. Here's our complete plan for environment activation feature in case you're interested: #20950. Cheers! |
Type: Bug
Behaviour
I tried finding related issues, best I could find is #11039
Expected vs. Actual
Expected
Only one environment activates in my open Terminal when the Python extension is activated.
I'm used to having my terminal auto activate conda and my environment with text when the terminal opens. It's cool that this works the other way, but this new behavior I think goes against the recommendations of Conda? See my
.zshrc
, if I remove that block thatconda init
automatically adds, then things work as expected -- cool?Actual
Somehow the environment
(dbt)
still is listed in parentheticals, but so is(base)
. This only happened to me a few week ago -- I've been using Code Insiders for over a year nowTo get it back to what I'm used to, I must call
conda deactivate
twice, thenconda activate dbt
(See below screenshot).Steps to reproduce:
.py
file to trigger opening of Python extensionDiagnostic data
python.languageServer
setting: DefaultOutput for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)User Settings
Extension version: 2023.19.12861011
VS Code version: Code - Insiders 1.84.0-insider (Universal) (eb4f3c149f34d82b9763a08230907cf79e7fc103, 2023-10-10T05:42:05.917Z)
OS version: Darwin arm64 22.6.0
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: