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
pytest provides the switch --pdb in order to enter a debugger whenever a test fails. In pytest-dev/pytest#1712 I added the --pdbcls flag to pytest so that one can specify an arbitrary Pdb subclass; e.g. one can call py.test --pdbcls=IPython.core.debugger:Pdb --pdb to use the ipython debugger instead.
Unfortunately it is currently not possible to pass in pudb (py.test --pdbcls=pudb.debugger:Debugger --pdb) because the Debugger.interaction method has a completely different signature than Pdb.interaction (which is the entry point used), leading to a crash of pytest. Specifically, the signatures are
Would it be possible to modify the signature of Debugger.interaction so that the second argument becomes, say, exc_tuple_or_traceback (to maintain backcompatibility and also be compatible with pytest)?
The text was updated successfully, but these errors were encountered:
pytest provides the switch
--pdb
in order to enter a debugger whenever a test fails. In pytest-dev/pytest#1712 I added the--pdbcls
flag to pytest so that one can specify an arbitraryPdb
subclass; e.g. one can callpy.test --pdbcls=IPython.core.debugger:Pdb --pdb
to use the ipython debugger instead.Unfortunately it is currently not possible to pass in pudb (
py.test --pdbcls=pudb.debugger:Debugger --pdb
) because theDebugger.interaction
method has a completely different signature thanPdb.interaction
(which is the entry point used), leading to a crash of pytest. Specifically, the signatures areand
Would it be possible to modify the signature of
Debugger.interaction
so that the second argument becomes, say,exc_tuple_or_traceback
(to maintain backcompatibility and also be compatible with pytest)?The text was updated successfully, but these errors were encountered: