55

I'm running a suite of tests (.py files) using nosetests. Using a classic

import pdb; pdb.set_trace()

the nosetests run just never completes. It just hangs right where the breakpoint has been set, but never drops into the pdb debugger.

Any ideas why this would be? I've tried moving the breakpoint to a number of different positions (other test functions, other files) to no avail.

Martijn Pieters
  • 1,048,767
  • 296
  • 4,058
  • 3,343
Bodhi
  • 1,437
  • 1
  • 13
  • 21

3 Answers3

61

Run nose with the -s / --nocapture option and you'll be able to see the pdb prompt and interact with the debugger normally.

If using the commandline that means:-

python manage.py  test -s [other-opts-and-args]
Himanshu
  • 2,384
  • 2
  • 24
  • 42
stderr
  • 8,567
  • 1
  • 34
  • 50
39

Nose is capturing the output and redirecting it. So, the breakpoint is hit, but you just don't see it. You need to turn off the output redirection so that the debug output shows up on the screen.

Nose can do this for you, if you use:

from nose.tools import set_trace; set_trace()

instead of:

import pdb;pdb.set_trace()
Joe L.
  • 1,888
  • 12
  • 14
0

In my case the flag the flag -s/--nocapture, still didn't resolve it and drop the compiler into pdb.

One other reason that you could look into is if you're using a database such as MySQL as part of your tests, that it's not locked by another simultaneous process. In my case, i had started a python shell to query the MySQL database through SQL Alchemy and that had locked up the tables. As a result, my nose tests were hanging - not running/exiting.

I killed the python processes which were locking up the tables and Nose was back up sniffing

> $ ps auxww | grep python | awk '{print $2}' | sudo xargs kill -9

Shankar ARUL
  • 12,642
  • 11
  • 68
  • 69