Skip to content

VS Code don't activate virtual python env on start #104647

@zensimilia

Description

@zensimilia

Issue Type: Bug

VS Code don't activate virtual python env automatically on start. Need to open new terminal to do this.

Create environment by command: python3 -m venv env

VS Code version: Code 1.48.0 (db40434, 2020-08-13T07:50:06.060Z)
OS version: Windows_NT ia32 6.1.7601

System Info
Item Value
CPUs Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz (4 x 3591)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 7.87GB (0.76GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (19)
Extension Author (truncated) Version
vscode-django bat 0.20.0
django-html bib 1.3.0
django-snippets bib 1.1.1
django big 1.0.2
flask-snippets cst 0.1.1
xml Dot 2.5.1
vsc-material-theme Equ 32.8.0
vsc-material-theme-icons equ 1.2.0
auto-close-tag for 0.5.8
vscode-auto-open-markdown-preview hnw 0.0.4
rest-client hum 0.24.1
vscode-django-boilerplate Men 1.6.0
python ms- 2020.8.101144
remote-ssh ms- 0.51.0
remote-ssh-edit ms- 0.51.0
vetur oct 0.26.1
material-icon-theme PKi 4.2.0
jinjahtml sam 0.15.0
jinja2-snippet-kit Wya 2.0.0

(1 theme extensions excluded)

Metadata

Metadata

Assignees

Labels

*caused-by-extensionIssue identified to be caused by an extension

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions