<?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: Jinja2 and django-registration</title>
	<atom:link href="http://www.davidcramer.net/code/486/jinja2-and-django-registration.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.davidcramer.net/code/486/jinja2-and-django-registration.html</link>
	<description>A blog about Django, JavaScript, CSS, and general web development.</description>
	<lastBuildDate>Fri, 12 Mar 2010 19:46:01 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jorge Vargas</title>
		<link>http://www.davidcramer.net/code/486/jinja2-and-django-registration.html/comment-page-1#comment-20995</link>
		<dc:creator>Jorge Vargas</dc:creator>
		<pubDate>Tue, 06 Oct 2009 02:36:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidcramer.net/?p=486#comment-20995</guid>
		<description>This is both awesome and scary at the same time. controllers as classes for the win :)</description>
		<content:encoded><![CDATA[<p>This is both awesome and scary at the same time. controllers as classes for the win <img src='http://www.davidcramer.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.davidcramer.net/code/486/jinja2-and-django-registration.html/comment-page-1#comment-20994</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 05 Oct 2009 20:22:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidcramer.net/?p=486#comment-20994</guid>
		<description>@teepark

That is definitely a way you could handle it. However you then lose the ability to interact with the original code as it was. In our project this isn&#039;t such a big deal, but the generic accessors in Coffin this definitely isn&#039;t a possibility.</description>
		<content:encoded><![CDATA[<p>@teepark</p>
<p>That is definitely a way you could handle it. However you then lose the ability to interact with the original code as it was. In our project this isn&#8217;t such a big deal, but the generic accessors in Coffin this definitely isn&#8217;t a possibility.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: teepark</title>
		<link>http://www.davidcramer.net/code/486/jinja2-and-django-registration.html/comment-page-1#comment-20993</link>
		<dc:creator>teepark</dc:creator>
		<pubDate>Mon, 05 Oct 2009 20:18:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidcramer.net/?p=486#comment-20993</guid>
		<description>seems pretty roundabout. if you know that the registration views are using render_to_response and RequestContext from their own global namespace, why not just monkeypatch?

registration.views.render_to_response = coffin.shortcuts.render_to_response
registration.views.RequestContext = coffin.template.RequestContext</description>
		<content:encoded><![CDATA[<p>seems pretty roundabout. if you know that the registration views are using render_to_response and RequestContext from their own global namespace, why not just monkeypatch?</p>
<p>registration.views.render_to_response = coffin.shortcuts.render_to_response<br />
registration.views.RequestContext = coffin.template.RequestContext</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars</title>
		<link>http://www.davidcramer.net/code/486/jinja2-and-django-registration.html/comment-page-1#comment-20988</link>
		<dc:creator>Lars</dc:creator>
		<pubDate>Thu, 01 Oct 2009 15:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidcramer.net/?p=486#comment-20988</guid>
		<description>This ticket may be of interest to you:
http://code.google.com/p/django-registration/issues/detail?id=132

http://bitbucket.org/ubernostrum/django-registration/issue/1/accept-template_loader-in-views</description>
		<content:encoded><![CDATA[<p>This ticket may be of interest to you:<br />
<a href="http://code.google.com/p/django-registration/issues/detail?id=132" rel="nofollow">http://code.google.com/p/django-registration/issues/detail?id=132</a></p>
<p><a href="http://bitbucket.org/ubernostrum/django-registration/issue/1/accept-template_loader-in-views" rel="nofollow">http://bitbucket.org/ubernostrum/django-registration/issue/1/accept-template_loader-in-views</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob</title>
		<link>http://www.davidcramer.net/code/486/jinja2-and-django-registration.html/comment-page-1#comment-20987</link>
		<dc:creator>Jacob</dc:creator>
		<pubDate>Thu, 01 Oct 2009 11:57:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidcramer.net/?p=486#comment-20987</guid>
		<description>You might also look at how django-smorgasbord does this.  I use it to use mako, currently, with 3rd party applications, but it should work with other template languages as well, including jinja2.  It involves a very minor monkeypatch to django&#039;s template loader, with the result that you can use several template systems at once.</description>
		<content:encoded><![CDATA[<p>You might also look at how django-smorgasbord does this.  I use it to use mako, currently, with 3rd party applications, but it should work with other template languages as well, including jinja2.  It involves a very minor monkeypatch to django&#8217;s template loader, with the result that you can use several template systems at once.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
