> Django "class views" are a product of brain damage, really
“Brain damage” is rather harsh: they're following a valid design principle but (IMO) carried a little further than the scope of the problem might require, running into the classic tradeoff versus ease of acquisition.
- Django regular views are ok (though not class based)
- Django "class views" are a product of brain damage, really (see the example to see what I mean)
This looks like sane class based views, but I was expecting something more like the way Pyramid does it (which are not generic, but class based)