I just did this last week.
I think it helps to provide some context for Django. View the architecture fro the outside in. Apache - mod_wsgi - Django - template presentation - view function - model.
I think it helps to look at an HTTP request's life cycle from browser to Apache to mod_wsgi to Django to the URL mapping to the view function to the template rendering.
I think that Python language features should be minimized. It's an easy language and can be discussed as side-bars.
Don't forget to briefly (very briefly) mention the essential features of Django -- url mapping, template rendering, ORM, application structuring, built-in admin pages.
I think that the real heart of the presentation should follow the Django tutorial style.
Look at models first. Cover just enough Python syntax and semantics to explain what the code sample means.
Look at URL mapping and view functions next. Keep these short. Focus on built-in master-detail views since they're so simple.
Look at template code last. Be sure to differential Django templates (which do very little) from JSP pages or PHP (which do too much.)
I think it's important to not waste much time on Python-isms. The language can spark useless debates on multiple-inheritance, compile-time type checking and the like.
I think it's important to dwell on the Django unittest features. Those are wonderful. We use them heavily.