GitMate.io thinks possibly related issues are https://github.com/pytest-dev/pytest/issues/472 (skipif documentation has broken example using pytest.config), https://github.com/pytest-dev/pytest/issues/390 (support pdb.set_trace() with pytest-xdist), https://github.com/pytest-dev/pytest/issues/1894 (pytest 3.0.+ and unicode), https://github.com/pytest-dev/pytest/issues/1932 (pytest --pdb is no longer working with Flask_testing), and https://github.com/pytest-dev/pytest/issues/399 (Debug output is invisible when using pytest with pdb and pyreadline (Windows)).
just install it and it will be used (i implemented the support for that trick for wheel based installs in pdb++)
@RonnyPfannschmidt Does it work with ipdb as well? With --pdb: What is the default debugger in case several are installed?
@fkromer psb++ replaces pdb with a interesting hack, ipdb needs own support like from pytest-ipdb
the default is always pdb usag
@RonnyPfannschmidt
i implemented the support for that trick for wheel based installs in pdb++
Thanks, wasn't aware of that.
I really like pdbpp and that it replaces pdb so well.
Maybe you could help reviewing some of my latest PRs for pdbpp to fix some issues in this regard? https://github.com/antocuni/pdb/pulls
I think this issue / question can be closed then.
@blueyed currently i'm no longer working on pdb++ - it's terminal ux library is unmaintained and i haven't found another maintainer for that (pyrepl)
Most helpful comment
just install it and it will be used (i implemented the support for that trick for wheel based installs in pdb++)