Class-based views with Django

Class-based views with Django Simon Willison DJUGL, 7th April 2009

Reusability A guiding principle of Django “Build applications, not projects” Generic views Thriving third party ecosystem

The Django contract A Django view is a function that takes a request object and returns a response object ORM, middleware, template language, forms, authentication system, admin, sites etc are all optional extras

Generic views Encapsulate common patterns in web development List of things / page about each things Things that are archived by date Things you can create/update/delete Let’s look at the code for object_detail

object_detail drawbacks You can’t swap the ORM for something else (without duck typing your own queryset) You have to use RequestContext You can’t modify something added to the context; you can only specify extra_context That’s despite a great deal of effort going in to making the behaviour customisable

newforms-admin De-coupled admin from the rest of Django Admin is just another application A new approach to customisation Powerful subclassing pattern

Finely grained permissions class Entry(models.Model): title = models.CharField(max_length=255) author = models.ForeignKey('auth.User') class EntryAdmin(admin.ModelAdmin): exclude = ('author',) def queryset(self, request): queryset = super(EntryAdmin, self).queryset(request) return queryset.filter(author = request.user) def save_model(self, request, obj, form, change): obj.author = request.user obj.save() def has_change_permission(self, request, ojb=None): if not obj: return True # access to change list return obj.author == request.user has_delete_permission = has_change_permission admin.site.register(Entry, EntryAdmin)

Objects can be views A Django view is a function that takes a request object and returns a response object A Django view is a callable that takes a request object and returns a response object

Objects can be views A Django view is a function that takes a request object and returns a response object A Django view is a callable that takes a request object and returns a response object Just deﬁne __call__() on the class

Example: restview.py http://www.djangosnippets.org/snippets/1071/

django_openid Next generation of my django-openid project Taken a lot longer than I expected Extensive use of class-based customisation

Ideas from django_openid Everything should go through a render() method Every template inherits from base_template Every decision should be a method Every form should come from a method Every model interaction should live in a method

TemplateResponse If you render_to_response, a subclass can’t override and reuse your method while modifying the context or template Solution: return TemplateResponse( request, 'article.html', context ) auth.py line 65

Class-based generic views Ticket #6735 Didn’t quite make 1.1; scheduled for 1.2

Subclassable decorators ratelimitcache is a decorator that implements rate limiting for a Django view It’s a class disguised as a function, using the __call__ method You can subclass it to customise its behaviour http://github.com/simonw/ratelimitcache/tree/master

Extending the contract Django view: take request / return response Django middleware: take request / return response Django application: take request / return response Django urlconf: take request / return response Django site: take request / return response

Thank you

http://c2.teckoo.com	127
http://www.slideshare.net	87
http://lanyrd.com	19
http://www.python.rk.edu.pl	16
http://webscope.posterous.com	11
http://teckoo.com	7
http://cncc.bingj.com	1
http://www.teckoo.com	1

Class-based views with Django

by Simon Willison

Accessibility

Categories

Upload Details

Usage Rights

8 Embeds 269

Statistics