Django 1.5 was changed in https://code.djangoproject.com/ticket/19316 so that `View.as_view` is really the only trouble-free entry point for a class-based view. Unfortunately that conflicts with django-flows' strategy of callig `View.dispatch` directly on `Action`s.
Django 1.5 was changed in https://code.djangoproject.com/ticket/19316 so
that `View.as_view` is really the only trouble-free entry point for a
class-based view. Unfortunately that conflicts with django-flows'
strategy of callig `View.dispatch` directly on `Action`s.

Reported:
https://groups.google.com/forum/#!topic/django-developers/a4SH3YJwAi4

After a lengthy IRC discussion we were promised a fix in Django 1.7,
until then we'll have to rely on the kludge of setting up the
magic attributes ourselves.

laterpay/django-flows