That's the best reason anyone has given so far, but say you only need the URL router, nothing is forcing you to use the views layer. Admittedly when you strip out that much stuff then a micro-framework probably is a better choice. For me however I know Django well, and don't see much to be gained by learning a micro-framework.
I don't know what to say about someone wanting to not learn, other than the old metaphorical:
"when all you have is a hammer, everything looks like a nail"
I suggest trying out some screwdrivers for a while.
Its not that I don't want to learn, its that I see more benefit in learning different things, rather than what appears to be a repeat of something I know fairly well (with parts subtracted).
The analogy is closer to choosing between a pair of pliers and a leatherman. Maybe a drill would be more useful.
Another problem with many of the existing big frameworks is that they don't do single page apps too well - A lot of stuff I do these days just doesn't need to be designed around the notion of composing templated widgets server side. I just want to ship static html/tpl/etc files and dynamically built data. Wrapping my head around pretending everything is a full page build gets a bit frustrating - why is the response to a query a view or *view? It's just a serialized model I'm pushing over the wire, or a remote function call. Pretending it is a view is a layer of cognitive overheard in between the work I'm doing and the data I'm using.