I think seeing the huge project structure after initializing a Rails app vs. a Django app is what keeps me away from Rails. I prefer a minimal starting base that lets me immediately make decisions about my app. I do need to give rails another chance though.
If anything you should prefer Rails in this case. Django generates fewer files, but what if you want to customize the automatic stuff? I'm talking about the admin templates, etc. You end up needing to copy the files over anyway.
I'd say the two give you the same amount of framework code to start with. Rails just happens to let you see and fiddle with it right off the bat.
In any case, when I start a new project I don't want to worry about creating a bunch of files and remembering where to put them and doing all this setup. I just need some sane defaults, so that I can start making actual project-related decisions instead of fooling around with "how do I want to arrange my files this time?"
It is possible to override admin templates while maintaining inheritance from the baked-in templates. You can check here: https://docs.djangoproject.com/en/1.3/ref/contrib/admin/#ove.... Anyway it is better to look at the admin not as part of the framework, but a bonus app you get to get started with modifying data.
