Skip to content

Commit f5349db

Browse files
committed
Add a note on how to run pudb so it doesn't fail
1 parent 9b0b3fe commit f5349db

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -94,8 +94,9 @@ Debugging
9494
Debugging works like you'd expect. You just use pdb, ipdb or pudb (ipdb
9595
and pudb seem to have a tendency not to work under the dev_appserver,
9696
but pdb is just fine). Rule is, use ipbd or pudb if you want to debug
97-
something that's called by a test, pdb for a live web application. Worst
98-
case scenario is that you just need to edit a little more. You can also
97+
something that's called by a test (run something like `pudb
98+
.env/bin/nosetests`), pdb for a live web application. Worst case
99+
scenario is that you just need to edit a little more. You can also
99100
easily use iPython to explore your ideas before you commit them to code.
100101

101102
![ipython prompt and ipdb in a test]

0 commit comments

Comments
 (0)