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
Python version (& distribution if applicable, e.g. Anaconda): N/A
Using VS Code or Visual Studio: N/A
Actual behavior
After extracting the wheel, I notice there are no PDB files for pydevd_frame_evaluator.cp39-win_amd64.pyd and pydevd_cython.cp39-win_amd64.pyd.
Expected behavior
After extracting the wheel, PDB files should either be there for pydevd_frame_evaluator.cp39-win_amd64.pyd and pydevd_cython.cp39-win_amd64.pyd, or symbols for those pyd files should be available for downstream consumption.
In a pwsh terminal, change the directory into the extracted folder and run Get-ChildItem -Path . -Filter "*.pdb" -Recurse and Get-ChildItem -Path . -Filter "*.pyd" -Recurse
🐛 There are no PDB files for pydevd_frame_evaluator.cp39-win_amd64.pyd and pydevd_cython.cp39-win_amd64.pyd.
The text was updated successfully, but these errors were encountered:
rzhao271
changed the title
any-any wheels include pyd files with missing symbols
py2.py3-none-any wheels include pyd files with missing symbols
Aug 13, 2024
Thanks for the issue but why should we ship pdb files? Seems like unnecessary bloat. If you want to debug the c++ code in debugpy, you can build it locally.
Before creating a new issue, please check the FAQ to see if your question is answered there.
Environment data
Actual behavior
After extracting the wheel, I notice there are no PDB files for pydevd_frame_evaluator.cp39-win_amd64.pyd and pydevd_cython.cp39-win_amd64.pyd.
Expected behavior
After extracting the wheel, PDB files should either be there for pydevd_frame_evaluator.cp39-win_amd64.pyd and pydevd_cython.cp39-win_amd64.pyd, or symbols for those pyd files should be available for downstream consumption.
Steps to reproduce:
Get-ChildItem -Path . -Filter "*.pdb" -Recurse
andGet-ChildItem -Path . -Filter "*.pyd" -Recurse
The text was updated successfully, but these errors were encountered: