Commit 349a1e7
committed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1,4 +1,4 @@ | |||
| 1 | - .. _authors: | ||
| 1 | + .. _bpaste: | ||
| 2 | 2 | ||
| 3 | 3 | bpaste | |
| 4 | 4 | ====== | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -0,0 +1,17 @@ | |||
| 1 | + .. _bpdb: | ||
| 2 | + | ||
| 3 | + bpdb | ||
| 4 | + ==== | ||
| 5 | + | ||
| 6 | + To enable bpython support within pdb, start pdb with the following code: | ||
| 7 | + | ||
| 8 | + .. code-block:: python | ||
| 9 | + | ||
| 10 | + import bpdb | ||
| 11 | + bpdb.set_trace() | ||
| 12 | + | ||
| 13 | + This will drop you into bpdb instead of pdb, which works exactly like pdb except | ||
| 14 | + that you can additionally start bpython at the current stack frame by issuing | ||
| 15 | + the command `Bpython` or `B`. | ||
| 16 | + | ||
| 17 | + You can exit bpython with `^D` to return to bpdb. | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -26,3 +26,4 @@ Contents: | |||
| 26 | 26 | sourcecode | |
| 27 | 27 | bpaste | |
| 28 | 28 | tips | |
| 29 | + bpdb | ||
0 commit comments