I went through the very same experience you're going through now, and ended up with Rails. The largest deciding factor was the size of the community in my geographic area. Sure, there's always going to be a nontrivial online community for any activity, and the online presence of Django is enough to keep you going. But, you'll need to get some face-to-face interaction in there -- at least I needed that when learning. Waiting for a message board post is not the same as asking a few questions back and forth with a more experienced developer.
My impression that I got from both communities is that while both are good at fostering the growth of existing members (most programming communities do this well). Django is really bad at "evangelism," via teaching non developers to code via Python/Django or converting existing devs over to the framework. In contrast, the Rails community is better than most for profit groups at this (think about Microsoft's initiatives vs. something like Rails for Zombies).
For an example, compare the two homepages. The Rails page is much better at actually conveying the it's information effectively than Django.
My impression that I got from both communities is that while both are good at fostering the growth of existing members (most programming communities do this well). Django is really bad at "evangelism," via teaching non developers to code via Python/Django or converting existing devs over to the framework. In contrast, the Rails community is better than most for profit groups at this (think about Microsoft's initiatives vs. something like Rails for Zombies).
For an example, compare the two homepages. The Rails page is much better at actually conveying the it's information effectively than Django.