David Cramer's Blog - Latest Comments in Jinja2 and django-registration

Re: Jinja2 and django-registration

Swing Sets — Mon, 29 Nov 2010 05:46:16 -0000

if you know that the registration views are using render_to_response and RequestContext from their own global namespace, why not just monkeypatch?

Re: Jinja2 and django-registration

Jorge Vargas — Mon, 05 Oct 2009 22:36:32 -0000

This is both awesome and scary at the same time. controllers as classes for the win :)

Re: Jinja2 and django-registration

David Cramer — Mon, 05 Oct 2009 16:22:46 -0000

@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't such a big deal, but the generic accessors in Coffin this definitely isn't a possibility.

Re: Jinja2 and django-registration

teepark — Mon, 05 Oct 2009 16:18:27 -0000

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

Re: Jinja2 and django-registration

Lars — Thu, 01 Oct 2009 11:18:40 -0000

This ticket may be of interest to you:
http://code.google.com/p/dj...

http://bitbucket.org/uberno...

Re: Jinja2 and django-registration

Jacob — Thu, 01 Oct 2009 07:57:20 -0000

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's template loader, with the result that you can use several template systems at once.