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

Python Debugger uses independent terminals #322

Closed
gogo16888 opened this issue Apr 22, 2024 · 1 comment
Closed

Python Debugger uses independent terminals #322

gogo16888 opened this issue Apr 22, 2024 · 1 comment
Assignees
Labels
triage-needed Needs assignment to the proper sub-team

Comments

@gogo16888
Copy link

Type: Bug

When starting a debugging session, it will automatically start one terminal, which is not consistent with the terminal that has already been started and set with environment variables.

Extension version: 2024.4.0
VS Code version: Code 1.88.1 (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:41:02.734Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 5.15.0-76-generic

  • Python version (& distribution if applicable, e.g. Anaconda): 3.11.8
  • Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
System Info
Item Value
CPUs Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz (12 x 2712)
GPU Status 2d_canvas: enabled
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
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Load (avg) undefined
Memory (System) 15.73GB (7.26GB free)
Process Argv --crash-reporter-id de2e0085-5a16-4788-a98f-931cb265feed
Screen Reader no
VM 60%
Item Value
Remote SSH: 84Server
OS Linux x64 5.15.0-76-generic
CPUs Intel(R) Core(TM) i7-9800X CPU @ 3.80GHz (16 x 3800)
Memory (System) 125.47GB (115.00GB free)
VM 0%
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
gee8j676:31009558
dsvsc021:30996838
f3je6385:31013174
pythoncenvpt:31022790

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Apr 22, 2024
@paulacamargo25
Copy link
Contributor

Thanks for your issue report, that is the default behaviour for the debugger, we are working on a feature to launch the debugger from the terminal, this should be done by the end of June.

@paulacamargo25 paulacamargo25 closed this as not planned Won't fix, can't repro, duplicate, stale May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

3 participants