You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
If workspaceFolder is specified in launch request, use it to force user code location #581
One thing that happens sometimes is that the user places its own code inside a site-packages.
In this case the debugger may end up ignoring user code as it's defined in a library folder when justMyCode:true. The idea would be that if workspaceFolder is passed on the launch request, its contents would be treated as user code.
Still, I haven't seen more reports lately on users not being able to debug due to having user code inside the site packages (probably more people are now aware they need to set "justMyCode":false to debug in that case and that structure is already not that common I think), so, not sure if we should do this or just leave at the current status quo...
Activity
int19h commentedon Apr 21, 2021
Hm, but then we'll also be treating any virtual environments in that folder as user code, including any third-party packages installed in them?
fabioz commentedon Jun 4, 2021
The debugger should be able to deal with cases where there's a structure as:
(the particular code is: https://github.com/microsoft/debugpy/blob/v1.3.0/src/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_filtering.py#L298)
So, that should still work...
Still, I haven't seen more reports lately on users not being able to debug due to having user code inside the site packages (probably more people are now aware they need to set
"justMyCode":falseto debug in that case and that structure is already not that common I think), so, not sure if we should do this or just leave at the current status quo...int19h commentedon Feb 1, 2023
No traction on this to date; closing until we decide we actually need it.