<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: New Django installation</title>
	<link>http://blog.go4teams.com/archives/new-django-installation/26</link>
	<description>What I Read; What I Have Read; and stuff I pick up and drag along</description>
	<pubDate>Mon,  6 Sep 2010 18:25:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: Daniel Tietze</title>
		<link>http://blog.go4teams.com/archives/new-django-installation/26#comment-24</link>
		<pubDate>Tue, 23 May 2006 10:21:22 +0000</pubDate>
		<guid>http://blog.go4teams.com/archives/new-django-installation/26#comment-24</guid>
					<description>&lt;p&gt;Archatas - Yes, I'm using PIL in my app. If I remember correctly, PIL was included in the SUSE 10 DVD as an RPM and I just installed it via Yast.
&lt;/p&gt;
P.S. Yeah - I just checked. I installed python-imaging-1.1.4-298, which comes with the SUSE distribution.</description>
		<content:encoded><![CDATA[<p>Archatas - Yes, I&#8217;m using PIL in my app. If I remember correctly, PIL was included in the SUSE 10 DVD as an RPM and I just installed it via Yast.
</p>
<p>P.S. Yeah - I just checked. I installed python-imaging-1.1.4-298, which comes with the SUSE distribution.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Archatas</title>
		<link>http://blog.go4teams.com/archives/new-django-installation/26#comment-23</link>
		<pubDate>Tue, 23 May 2006 09:26:18 +0000</pubDate>
		<guid>http://blog.go4teams.com/archives/new-django-installation/26#comment-23</guid>
					<description>BTW, did you manage to install PIL (Python Imaging Library) on SUSE Linux as well? PIL tends to be used by Image Field in Django. If you installed that library succesfully, could you share your experiences about that?</description>
		<content:encoded><![CDATA[<p>BTW, did you manage to install PIL (Python Imaging Library) on SUSE Linux as well? PIL tends to be used by Image Field in Django. If you installed that library succesfully, could you share your experiences about that?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Archatas</title>
		<link>http://blog.go4teams.com/archives/new-django-installation/26#comment-22</link>
		<pubDate>Tue, 23 May 2006 08:05:02 +0000</pubDate>
		<guid>http://blog.go4teams.com/archives/new-django-installation/26#comment-22</guid>
					<description>I think, another way to solve your problem was to create appropriate symlinks, so that the required directories were found on the python path.</description>
		<content:encoded><![CDATA[<p>I think, another way to solve your problem was to create appropriate symlinks, so that the required directories were found on the python path.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: import this. &#187; Blog Archive &#187; Django and 64-bit Linux</title>
		<link>http://blog.go4teams.com/archives/new-django-installation/26#comment-13</link>
		<pubDate>Sun, 26 Mar 2006 04:20:51 +0000</pubDate>
		<guid>http://blog.go4teams.com/archives/new-django-installation/26#comment-13</guid>
					<description>[...] Daniel just got a new box with a 64-bit processor, so he is moving his Django project over to it. But he ran into some problems: It appears that the Python packaging tool is confused by the fact that 64 bit SUSE puts Python stuff under /usr/lib64 instead of /usr/lib and then assumes that it was installed to a non-standard location which isn’t on any Python path. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Daniel just got a new box with a 64-bit processor, so he is moving his Django project over to it. But he ran into some problems: It appears that the Python packaging tool is confused by the fact that 64 bit SUSE puts Python stuff under /usr/lib64 instead of /usr/lib and then assumes that it was installed to a non-standard location which isn’t on any Python path. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
