Skip to content
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

Cannot deactivate virtualenv in terminal #22118

Closed
gpratte-outbox opened this issue Sep 29, 2023 · 2 comments
Closed

Cannot deactivate virtualenv in terminal #22118

gpratte-outbox opened this issue Sep 29, 2023 · 2 comments
Labels
info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team

Comments

@gpratte-outbox
Copy link

Type: Bug

Since very recently vscode is activating the current virtualenv in my terminal, but using some new technique where the 'deactivate' command does not exists. I need to have a terminal free of the virtual env but I cannot unload it.

Extension version: 2023.16.0
VS Code version: Code 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:51:20.981Z)
OS version: Linux x64 6.5.0-1-amd64
Modes:

System Info
Item Value
CPUs AMD Ryzen 9 5950X 16-Core Processor (32 x 2879)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
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: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Load (avg) 2, 3, 2
Memory (System) 62.71GB (39.98GB free)
Process Argv --unity-launch --crash-reporter-id 655256e3-bc78-4502-b5f9-1545c0fbc383
Screen Reader no
VM 0%
DESKTOP_SESSION gnome
XDG_CURRENT_DESKTOP GNOME
XDG_SESSION_DESKTOP gnome
XDG_SESSION_TYPE wayland
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263:30792226
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
3biah626:30602489
f6dab269:30613381
a9j8j154:30646983
showlangstatbar:30737416
962ge761:30841074
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
asynctok:30821568
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
dsvsc015:30845448

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Sep 29, 2023
@gpratte-outbox
Copy link
Author

I've turned off both A/B tests and the virtual env terminal feature and not I no longer have the virtualenv. When A/B test was on though the virtual env terminal feature configuration was ignored...

@karrtikr
Copy link

Hello @gpratte-outbox, you might've run into https://github.com/microsoft/vscode-python/wiki/Activate-Environments-in-Terminal-Using-Environment-Variables. Known issue section provides a workaround for this limitation when A/B experiment and virtual env feature is on, let us know if you're still having trouble and we'll be happy to have a deeper look.

@karrtikr karrtikr closed this as not planned Won't fix, can't repro, duplicate, stale Sep 30, 2023
@github-actions github-actions bot added the info-needed Issue requires more information from poster label Sep 30, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 31, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

2 participants