<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: More on debugging Django</title>
	<atom:link href="http://djangodays.com/2008/10/08/more-on-debugging-django/feed/" rel="self" type="application/rss+xml" />
	<link>http://djangodays.com/2008/10/08/more-on-debugging-django/</link>
	<description>A growing collection of all things Django</description>
	<lastBuildDate>Sun, 18 Apr 2010 06:31:10 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Josh</title>
		<link>http://djangodays.com/2008/10/08/more-on-debugging-django/comment-page-1/#comment-2658</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Tue, 05 May 2009 14:15:57 +0000</pubDate>
		<guid isPermaLink="false">http://djangodays.com/?p=46#comment-2658</guid>
		<description>I have found that the easiest way to debug Django apps is to just run mange.py inside of Eclipse.  With Eclipse and PyDev, you have all of the features of a good debugger.  This has saved me a huge amount of time for my projects.

Cheers!
-Josh</description>
		<content:encoded><![CDATA[<p>I have found that the easiest way to debug Django apps is to just run mange.py inside of Eclipse.  With Eclipse and PyDev, you have all of the features of a good debugger.  This has saved me a huge amount of time for my projects.</p>
<p>Cheers!<br />
-Josh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joost</title>
		<link>http://djangodays.com/2008/10/08/more-on-debugging-django/comment-page-1/#comment-448</link>
		<dc:creator>Joost</dc:creator>
		<pubDate>Thu, 11 Dec 2008 07:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://djangodays.com/?p=46#comment-448</guid>
		<description>Ah great, i see you already found a solution!</description>
		<content:encoded><![CDATA[<p>Ah great, i see you already found a solution!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Milan Andric</title>
		<link>http://djangodays.com/2008/10/08/more-on-debugging-django/comment-page-1/#comment-447</link>
		<dc:creator>Milan Andric</dc:creator>
		<pubDate>Thu, 11 Dec 2008 04:50:09 +0000</pubDate>
		<guid isPermaLink="false">http://djangodays.com/?p=46#comment-447</guid>
		<description>I&#039;m looking for a solution to this problem http://groups.google.com/group/django-users/browse_frm/thread/af9073d32f1221a

I am able to add set_trace() in my code, but I don&#039;t know how to step through the code to get to the exception and then trigger the shell. I need to see what file is causing the failed import.  

If you could expand a bit on your post and give an example of how you might debug an import statement in a template exception that would help me a bit.  possibly help some others since set_trace() seems quite useful.  if I figure this out I will also try to write a post about it.</description>
		<content:encoded><![CDATA[<p>I&#8217;m looking for a solution to this problem <a href="http://groups.google.com/group/django-users/browse_frm/thread/af9073d32f1221a" rel="nofollow">http://groups.google.com/group/django-users/browse_frm/thread/af9073d32f1221a</a></p>
<p>I am able to add set_trace() in my code, but I don&#8217;t know how to step through the code to get to the exception and then trigger the shell. I need to see what file is causing the failed import.  </p>
<p>If you could expand a bit on your post and give an example of how you might debug an import statement in a template exception that would help me a bit.  possibly help some others since set_trace() seems quite useful.  if I figure this out I will also try to write a post about it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
