I found this gem few months back and I havent looked back ever since. My debug print statements have dropped a lot ever since.

Although I should mention I use a different flavor of the same idea. I first drop to pdb and then invoke ipython from there. That way when I quit out of ipython, i can go back and forth and maybe go into ipython again.



the way I do is.

import pdb;pdb.set_trace() > this goes inside the program

and inside pdb prompt
(pdb) invoke ipython

@Jeff
There is no such command in pdb as 'invoke'. Can you correct this? I find this technique very interesting.

Similar to pdb there is the ipython version ipdb.

import ipdb; ipdb.set_trace()

@ Art

Sorry if confused you folks. When I said 'invoke ipython' I meant invoke ipython in the way mentioned in the article.

ipdb is a wonderful contribution. would be cool to see it merged into IPython itself...

Whoa! nice one thanks.

Don't forget winpdb as an alternative to pdb or ipdb. It can attach to an already running program when you use set_trace().

Sweet! Something so simple yet so awesomely useful :)
I'm not sure if I'll ever use print to debug again

This is a good informational blog.That blog is very very importat for all human to know for there it sector and this blog authority.Thank you so much for the blog.