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 extension can not enter debug mode in vscode vesion 1.69.1 #19467

Closed
jxliaocb opened this issue Jul 14, 2022 · 3 comments
Closed

Python extension can not enter debug mode in vscode vesion 1.69.1 #19467

jxliaocb opened this issue Jul 14, 2022 · 3 comments
Labels
triage-needed Needs assignment to the proper sub-team

Comments

@jxliaocb
Copy link

Issue Type: Bug

  1. create launch.json file.
  2. crate a test.py file and add print("hello")
  3. set a breakpoint in test.py first line.
  4. click "Start and Debugging(F5)"

Can't enter arriave at breakpoint. and also no Python debug console in Terminal.

Extension version: 2022.10.0
VS Code version: Code 1.69.1 (b06ae3b2d2dbfe28bca3134cc6be65935cdfea6a, 2022-07-12T08:28:29.328Z)
OS version: Linux x64 5.14.0-1045-oem
Restricted Mode: No

System Info
Item Value
CPUs 11th Gen Intel(R) Core(TM) i7-1195G7 @ 2.90GHz (8 x 2900)
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
skia_renderer: enabled_on
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) 1, 2, 2
Memory (System) 15.35GB (3.93GB free)
Process Argv --unity-launch --crash-reporter-id dd19544d-1b0f-4098-9ccf-e8e019dbbd1f
Screen Reader no
VM 0%
DESKTOP_SESSION ubuntu
XDG_CURRENT_DESKTOP Unity
XDG_SESSION_DESKTOP ubuntu
XDG_SESSION_TYPE x11
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vsclangdf:30486550

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Jul 14, 2022
@AngryCochinoPup
Copy link

Are you running python3.6? If so, this update breaks debugging. Downgrade to the last version to fix.

@JosiahMendes
Copy link

Also had this same issue on a Windows host with Remote SSH into a Linux machine. Resolved temporarily by downgrading the extension.

@karthiknadig
Copy link
Member

Python 3.6 is deprecated upstream by python.org. So debugpy dropped it as well. See here for more info
#19427 (comment)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

4 participants