Here's my problem with all of these articles with the rails versus django battle-to-find-the-one-right-answer approach rather than rails and django different-arrows-in-the-quiver: they always seem to focus way down at too small a level of detail in their comparisons. I understand that being a programmer means being down in the trenches with the framework every day, so the temptation is to assume the important differences are down at that altitude as well and that's where the focus of any comparison should be. But it's totally wrong - they're just different at that level (not necessarily better or worse) and the important difference is at the higher level of what these tools are good at. And for that, you can look to where they came from to see their overall focus:
Rails -> came from building a web app (Basecamp) -> great for building apps, has to be rejiggered a bit for web sites
Django -> came from building a web site (several newspaper sites in Lawrence, Kansas) -> great for building sites, has to be rejiggered a bit for web apps
The idea for this has been building in my head for a while now and was solidified when I saw the creators of each framework say basically the same thing in a video showdown a few years back: