Local variables not displayed in Jupyter Panel during debugging with Python 3.13.0 in VS Code

[profRidha]

Type: Bug

This issue with the Jupyter extension in Visual Studio Code occurs when debugging a Python script that reaches a function. In this case, the local variables of the function are correctly displayed in the "Run and Debug" sidebar, but they do not appear in the Jupyter panel, which only shows the message "loading variables." This bug seems to be specific to the new Python version 3.13.0 and does not affect previous versions. It could be due to changes in the handling of local variables or in the debugging interface between Python and Jupyter in Visual Studio Code, possibly requiring adjustments in the extension to ensure compatibility with this latest version.

Extension version: 2024.11.2024102401
VS Code version: Code 1.95.0 (912bb683695358a54ae0c670461738984cbb5b95, 2024-10-28T20:16:24.561Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (4 x 3293)
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 webnn: disabled_off
Load (avg)	undefined
Memory (System)	3.90GB (0.44GB free)
Process Argv	--crash-reporter-id 112baf61-ccbc-43d1-90db-9e4d7a969c3f
Screen Reader	no
VM	0%

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
vscrp:30673768
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
945dj816:31013170
dvdeprecation:31068756
dwnewjupyter:31046869
newcmakeconfigv2:31071590
impr_priority:31102340
nativerepl1:31139838
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31132770
nativeloc2:31134642
wkspc-ranged-t:31151552
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013

[profRidha]

Will this bug be fixed after updating Python to version 3.13.1 ?