Hello!
* holger krekel [2014-09-15 07:13]:
What we probabl need is a new hook, pytest_enter_pdb maybe, which
pytest-timeout can implement to switch off timeout handling.
pytest would call this hook in the pdb.set_trace() interception
code around _pytest/pdb.py:34.
If that's
Hi Wolfgang,
On Mon, Sep 15, 2014 at 08:19 +0200, Wolfgang Schnerring wrote:
Hi,
thanks for your feedback!
* Bruno Oliveira [2014-09-13 15:53]:
1. Am I missing something or does pytest indeed completely seal off its
internals?
Not really, you can access _pytest module directly:
Hi Wolfgang, Bruno,
On Sat, Sep 13, 2014 at 15:53 -0300, Bruno Oliveira wrote:
Hi,
1. Am I missing something or does pytest indeed completely seal off its
internals?
Not really, you can access _pytest module directly:
import _pytest.pdb
_pytest.pdb.pytestPDB
class
Hi,
What we probabl need is a new hook, pytest_enter_pdb maybe, which
pytest-timeout can implement to switch off timeout handling.
pytest would call this hook in the pdb.set_trace() interception
code around _pytest/pdb.py:34.
I like this idea, seems simple enough to implement. :)
Cheers,
Hi,
I'd really love for pytest_timeout to not perform the timeout when I'm using
pdb (more specifically, the import pdb; pdb.set_trace() statement; I'm
aware that pytest_timeout learned to respect the --pdb command line
parameter recently), because it invariably bites me and then I have to
re-run
