One thing you should be aware of is that Django's philosophy is to cleanly separate between what designers do and what developers do. That's why you don't (by default) get to use Python in your view templates as you would in php/jsp/rails. Instead Django provides yet another mini language just for views, including control sturctures, expressions, etc.

If you are a designer and developer in one person, Django might not be the best match for you, unless you love something else about it (there are many things to love about Django)

I found that I don't use most of what web frameworks provide. But you could argue that just using Django's nice regex based request dispatching is worth it, even if you decide not to use their template engine at all (it's replaceable after all)

To sum it up, what is it that web frameworks do for you? It's basically request dispatching, forms processing (validation and stuff), view templates and ORM. If your applications handle a lot of form to database CRUD, using a framework is helpful. Otherwise you could just as well use naked mod_python because request dispatching is actually rather trivial and python already has a simple template engine built into the language.