<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Django Days &#187; Errors</title>
	<atom:link href="http://djangodays.com/category/errors/feed/" rel="self" type="application/rss+xml" />
	<link>http://djangodays.com</link>
	<description>A growing collection of all things Django</description>
	<lastBuildDate>Tue, 20 Apr 2010 05:58:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>More on debugging Django</title>
		<link>http://djangodays.com/2008/10/08/more-on-debugging-django/</link>
		<comments>http://djangodays.com/2008/10/08/more-on-debugging-django/#comments</comments>
		<pubDate>Wed, 08 Oct 2008 13:59:21 +0000</pubDate>
		<dc:creator>Joost</dc:creator>
				<category><![CDATA[Django]]></category>
		<category><![CDATA[Errors]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[debugging]]></category>

		<guid isPermaLink="false">http://djangodays.com/?p=46</guid>
		<description><![CDATA[The other day, I read about another interesting way of debugging Django Apps:
If you use the following statement in you code:
import pdb; pdb.set_trace()
You can debug you app by running the server with the python command
manage.py runserver -p 8888
Then, after you visit the page where the set_trace() function is called, the server will break the code [...]]]></description>
			<content:encoded><![CDATA[<p>The other day, I read about another interesting way of debugging Django Apps:</p>
<p>If you use the following statement in you code:<br />
<code>import pdb; pdb.set_trace()</code></p>
<p>You can debug you app by running the server with the python command<br />
<code>manage.py runserver -p 8888</code></p>
<p>Then, after you visit the page where the set_trace() function is called, the server will break the code execution. If you then go to your terminal window, it will show you a prompt, at which you can go throught your code and variables.</p>
<p>Pretty good stuff!!</p>
]]></content:encoded>
			<wfw:commentRss>http://djangodays.com/2008/10/08/more-on-debugging-django/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Error using New Comments in Django 1.0</title>
		<link>http://djangodays.com/2008/09/07/error-using-new-comments-in-django-10/</link>
		<comments>http://djangodays.com/2008/09/07/error-using-new-comments-in-django-10/#comments</comments>
		<pubDate>Sun, 07 Sep 2008 10:21:26 +0000</pubDate>
		<dc:creator>Joost</dc:creator>
				<category><![CDATA[Errors]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Django 1.0]]></category>

		<guid isPermaLink="false">http://djangodays.com/?p=21</guid>
		<description><![CDATA[After upgrading to Django 1.0 I got the following error when using the new comment framework in one of my templates:
Caught an exception while rendering: Reverse for '' not found. 
After some searching I read somewhere I had to delete the old .pyc files (from before the Django upgrade). After doing that, everything worked as [...]]]></description>
			<content:encoded><![CDATA[<p>After upgrading to Django 1.0 I got the following error when using the new comment framework in one of my templates:</p>
<p><code>Caught an exception while rendering: Reverse for '' not found. </code></p>
<p>After some searching I read somewhere I had to delete the old .pyc files (from before the Django upgrade). After doing that, everything worked as it should!</p>
<p>Also, make sure you have the right path in your urls.py:<br />
<code>(r'^comments/', include('django.contrib.comments.urls')),</code></p>
<p>Hope this is usefull to anyone!</p>
]]></content:encoded>
			<wfw:commentRss>http://djangodays.com/2008/09/07/error-using-new-comments-in-django-10/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Django ImageField validation error caused by incorrect PIL installation on MAC</title>
		<link>http://djangodays.com/2008/09/03/django-imagefield-validation-error-caused-by-incorrect-pil-installation-on-mac/</link>
		<comments>http://djangodays.com/2008/09/03/django-imagefield-validation-error-caused-by-incorrect-pil-installation-on-mac/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 06:07:18 +0000</pubDate>
		<dc:creator>Joost</dc:creator>
				<category><![CDATA[Errors]]></category>
		<category><![CDATA[Error]]></category>
		<category><![CDATA[ImageField]]></category>
		<category><![CDATA[PIL]]></category>

		<guid isPermaLink="false">http://djangodays.com/?p=17</guid>
		<description><![CDATA[I kept getting a validation error in the django admin pages while trying to upload an image. The validation error said: 
Upload a valid image. The file you uploaded was either not an image or
a corrupted. 
I really broke my brains on this one but finally got it to work! I knew for sure that [...]]]></description>
			<content:encoded><![CDATA[<p>I kept getting a validation error in the django admin pages while trying to upload an image. The validation error said: </p>
<blockquote><p><em>Upload a valid image. The file you uploaded was either not an image or<br />
a corrupted.</em> </p></blockquote>
<p>I really broke my brains on this one but finally got it to work! I knew for sure that the image was not corrupted so it had to be something else. After some googling I found a couple of pages on the Python Imagina Library and how it was kinda difficult to get that installed properly on MacOS. When I first installed Django I just used the standard &#8220;python setup.py install&#8221; command for installing PIL, but that did not install it correctly.</p>
<p>What worked for me was the following:</p>
<ol>
<li>Install the Apple XCodeTools (Either from the MacOS X install CD or register and download them <a title="Apple XCode Download" href="http://developer.apple.com/tools/xcode/">here)</a></li>
<li>Install the libjpeg for JPEG support by downloading the source <a title="Download libjpeg" href="http://www.ijg.org/files/jpegsrc.v6b.tar.gz">here</a>. Extract the downloaded file and move into the directory (most likely called &#8220;jpeg-6b&#8221;). Then type:<br />
<code>cp /usr/share/libtool/config.sub .<br />
cp /usr/share/libtool/config.guess .<br />
./configure –enable-shared<br />
make<br />
sudo mkdir -p /usr/local/include<br />
sudo mkdir -p /usr/local/bin<br />
sudo mkdir -p /usr/local/lib<br />
sudo mkdir -p /usr/local/man/man1<br />
sudo make install</code>
 </li>
<li>Now for correctly installing PIL: Download it <a title="Download Python Imaging Library" href="http://www.pythonware.com/products/pil/">here</a>. Unpack it and change the setup.py file:<br />
Change:<br />
<code>JPEG_ROOT = none<br />
ZLIB_ROOT = none</code><br />
to<br />
<code>JPEG_ROOT = “/usr/local/include”<br />
ZLIB_ROOT = “/usr/local/include” </code><br />
then run<br />
<code>python setup.py build_ext -i<br />
python selftest.py<br />
sudo python setup.py install</code></li>
</ol>
<p>That should be it! Hope that helps anyone!</p>
]]></content:encoded>
			<wfw:commentRss>http://djangodays.com/2008/09/03/django-imagefield-validation-error-caused-by-incorrect-pil-installation-on-mac/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>
