<?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: Waiting For Python Web Frameworks</title>
	<atom:link href="http://hivearchive.com/2006/04/23/waiting-for-python-web-frameworks/feed/" rel="self" type="application/rss+xml" />
	<link>http://hivearchive.com/2006/04/23/waiting-for-python-web-frameworks/</link>
	<description>Matt Michie&#039;s rants, raves, and thoughts</description>
	<lastBuildDate>Thu, 11 Feb 2010 00:36:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Massimo</title>
		<link>http://hivearchive.com/2006/04/23/waiting-for-python-web-frameworks/comment-page-1/#comment-15864</link>
		<dc:creator>Massimo</dc:creator>
		<pubDate>Tue, 30 Oct 2007 04:36:58 +0000</pubDate>
		<guid isPermaLink="false">http://hivearchive.com/2006/04/23/waiting-for-python-web-frameworks/#comment-15864</guid>
		<description>Hi Matt, 
Perahps you could take a look at Gluon (http://mdp.cti.depaul.edu). I would like to know your thoughts about it since they could help me improve Gluon.</description>
		<content:encoded><![CDATA[<p>Hi Matt,<br />
Perahps you could take a look at Gluon (<a href="http://mdp.cti.depaul.edu" rel="nofollow">http://mdp.cti.depaul.edu</a>). I would like to know your thoughts about it since they could help me improve Gluon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Bennett</title>
		<link>http://hivearchive.com/2006/04/23/waiting-for-python-web-frameworks/comment-page-1/#comment-25</link>
		<dc:creator>James Bennett</dc:creator>
		<pubDate>Thu, 27 Apr 2006 15:47:21 +0000</pubDate>
		<guid isPermaLink="false">http://hivearchive.com/2006/04/23/waiting-for-python-web-frameworks/#comment-25</guid>
		<description>FWIW, Django *didn&#039;t* reinvent the wheel; when Django was born as an internal project some years ago, the tools TurboGears brings together either didn&#039;t exist, or were in unusable states. Rails is in a similar situation -- at the time that Basecamp was developed, there weren&#039;t good lightweight tools that could be cobbled together into a framework, so they rolled their own.</description>
		<content:encoded><![CDATA[<p>FWIW, Django *didn&#8217;t* reinvent the wheel; when Django was born as an internal project some years ago, the tools TurboGears brings together either didn&#8217;t exist, or were in unusable states. Rails is in a similar situation &#8212; at the time that Basecamp was developed, there weren&#8217;t good lightweight tools that could be cobbled together into a framework, so they rolled their own.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: import this. &#187; Blog Archive &#187; Django API changes before 1.0</title>
		<link>http://hivearchive.com/2006/04/23/waiting-for-python-web-frameworks/comment-page-1/#comment-24</link>
		<dc:creator>import this. &#187; Blog Archive &#187; Django API changes before 1.0</dc:creator>
		<pubDate>Wed, 26 Apr 2006 12:06:18 +0000</pubDate>
		<guid isPermaLink="false">http://hivearchive.com/2006/04/23/waiting-for-python-web-frameworks/#comment-24</guid>
		<description>[...] Matt Michie is waiting for Python web frameworks, and mentions the changes in the Django project: Unfortunately, I started coding in Django right before the “magic” removal branch went public. The documentation didn’t mention anything about a massive API change that seems to require lots of changes to any code you write. Not that it is too important to me, it will be faster for me to start over and move the methods into the new branch. Still frustrating. [...]</description>
		<content:encoded><![CDATA[<p>[...] Matt Michie is waiting for Python web frameworks, and mentions the changes in the Django project: Unfortunately, I started coding in Django right before the “magic” removal branch went public. The documentation didn’t mention anything about a massive API change that seems to require lots of changes to any code you write. Not that it is too important to me, it will be faster for me to start over and move the methods into the new branch. Still frustrating. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: everes</title>
		<link>http://hivearchive.com/2006/04/23/waiting-for-python-web-frameworks/comment-page-1/#comment-7</link>
		<dc:creator>everes</dc:creator>
		<pubDate>Tue, 25 Apr 2006 04:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://hivearchive.com/2006/04/23/waiting-for-python-web-frameworks/#comment-7</guid>
		<description>Documentation about changes is here.
http://code.djangoproject.com/wiki/RemovingTheMagic</description>
		<content:encoded><![CDATA[<p>Documentation about changes is here.<br />
<a href="http://code.djangoproject.com/wiki/RemovingTheMagic" rel="nofollow">http://code.djangoproject.com/wiki/RemovingTheMagic</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
