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
This is something pdbpp should fix, because they actually hacked pdb so pdb.set_trace can point to their code, instead of real pdb. If you are monkey patching the standard library, it's your responsibility to sync everything. I believe they did it to make pdbpp a "drop in replacement" - that after installing the package (and probably importing it) you don't need to do anything special to bring it up.
However, for a normal derived debugger, they should not rely on pdb.set_trace to bring up their debugger, and they should be able to control everything. This new feature itself should not break any code unless they are doing something shady.
Uh oh!
There was an error while loading. Please reload this page.
Bug report
Bug description:
Works fine with pdb:
However, after installing pdbpp 0.11.6 (which has recently been forked and resurrected):
(Python 3.13 works as expected.)
This is because the
commands
argument has been added in 3.14:https://docs.python.org/3.14/library/pdb.html#pdb.set_trace
And it's likely that pdbpp has subclassed
Pdb
and doesn't yet supportcommands
.@gaogaotiantian Is this something that pdb or pdbpp should fix?
I've not tested other debuggers.
CPython versions tested on:
3.14
Operating systems tested on:
macOS
The text was updated successfully, but these errors were encountered: