docs | |
tests | |
package |
Remote vanilla PDB (over TCP sockets) done right: no extras, proper handling around connection failures and CI. Based on pdbx.
- Free software: BSD 2-Clause License
pip install remote-pdb
To open a remote PDB on first available port:
from remote_pdb import set_trace
set_trace() # you'll see the port number in the logs
To use some specific host/port:
from remote_pdb import RemotePdb
RemotePdb('127.0.0.1', 4444).set_trace()
To connect just run telnet 127.0.0.1 4444
. When you are finished debugging, either exit the debugger, or press Control-], then Control-d.
Alternately, one can connect with NetCat: nc -C 127.0.0.1 4444
or Socat: socat readline tcp:127.0.0.1:4444
(for line editing and history support). When finished debugging, either exit the debugger, or press Control-c.
If you are using Python 3.7 one can use the new breakpoint()
built in to invoke remote PDB. In this case the following environment variable must be set:
PYTHONBREAKPOINT=remote_pdb.set_trace
The debugger can then be invoked as follows, without any imports:
breakpoint()
As the breakpoint()
function does not take any arguments, environment variables can be used to specify the host and port that the server should listen to. For example, to run script.py
in such a way as to make telnet 127.0.0.1 4444
the correct way of connecting, one would run:
PYTHONBREAKPOINT=remote_pdb.set_trace REMOTE_PDB_HOST=127.0.0.1 REMOTE_PDB_PORT=4444 python script.py
If REMOTE_PDB_HOST
is omitted then a default value of 127.0.0.1 will be used. If REMOTE_PDB_PORT
is omitted then the first available port will be used. The connection information will be logged to the console, as with calls to remote_pdb.set_trace()
.
In certain scenarios (backgrounded processes) OS X will prevent readline to be imported (and readline is a dependency of pdb). A workaround (run this early):
import signal
signal.signal(signal.SIGTTOU, signal.SIG_IGN)
See #9 and cpython#14892.
Python 2.6, 2.7, 3.2, 3.3 and PyPy are supported.