Re: csrf migration

2010-02-10 Thread Russell Keith-Magee
On Thu, Feb 11, 2010 at 12:22 PM, Jeff Bauer wrote: > Update: My work-around is this: > > 1) Wrap views functions: >    try: >        import django.views.decorators.csrf >        # Django 1.2 stuff >    except ImportError: >        # Django 1.1 stuff > > 2) If running Django 1.1, register a fake c

Re: csrf migration

2010-02-10 Thread Jeff Bauer
Update: My work-around is this: 1) Wrap views functions: try: import django.views.decorators.csrf # Django 1.2 stuff except ImportError: # Django 1.1 stuff 2) If running Django 1.1, register a fake custom tag 'csrf_token' and load it in the templates so it's

csrf migration

2010-02-10 Thread Jeff Bauer
It looks to be a long week of working out backwards incompatible stuff in Django-1.2 (beta-1). http://docs.djangoproject.com/en/dev/ref/contrib/csrf/ But I wish there were a gentler upgrade path. My main question: Is there a way to re-code my applications so the same codebase can run on both