Hi Julian & Bastian

Does pydevd have a similar patch upstream?

A PR for that was coincidentally opened this morning and Bastian already uploaded pydevd to unstable with that PR applied (thanks!).

It's not actually enough to fix debugpy though - still lots of failing tests (that take an hour or two to completely fail).

I think that update to pydevd might be incomplete in that it only updated the .py files and didn't cythonise. Upstream's release instructions seem to indicate that needs to be done and the results are checked in.

Comparing the Python 3.15 PR for debugpy's embedded pydevd and the one for pydevd that is in the 3.5.0+ds-4 Debian package, there are additional C and pyx files being changed:

https://github.com/fabioz/PyDev.Debugger/pull/330/changes

https://github.com/microsoft/debugpy/pull/2069/changes

- src/debugpy/_vendored/pydevd/_pydevd_sys_monitoring/_pydevd_sys_monitoring_cython.c - src/debugpy/_vendored/pydevd/_pydevd_sys_monitoring/_pydevd_sys_monitoring_cython.pyx

As a quick test of this, I just did a test build of debugpy disabling the compiled modules in pydevd (export PYDEVD_USE_CYTHON=no) and the test suite succeeded.

I *think* this in indicates a problem that needs resolving in
python3-pydevd and then debugpy will be happy (with what is already in git).

Does that make sense to either of you and do you know what needs to be done?

regards
Stuart



--
Stuart Prescott   http://www.nanonanonano.net/ [email protected]
Debian Developer  http://www.debian.org/       [email protected]
GPG fingerprint   90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Reply via email to