You can't go wrong with any of them. I think Django has a slight edge by having a slower release cycle. I find it a desirable quality in a development framework.
While the number of man-months spent developing Rails is an order of magnitude greater than that spent developing Django, is it really that much better for the bottom line?
Most of the early efforts spent on Rails were to make the infrastructure and community more mature. Even the brilliant DHH was a PHP developer before he started Rails.
On the other hand, Django benefited a lot from Python's maturity.
There is no easy way to measure this. But to support my point:
Rails first public release: July 2004 (5 years back)
Django's first public release: July 2005 (4 years back)
Rails Contributors: 1350
Django Contributors: 460
I never said that Django's community was smaller. I just said that it was more mature in their programming language and therefore it was easier for them to get things done right the first time.
While the number of man-months spent developing Rails is an order of magnitude greater than that spent developing Django, is it really that much better for the bottom line?
Most of the early efforts spent on Rails were to make the infrastructure and community more mature. Even the brilliant DHH was a PHP developer before he started Rails.
On the other hand, Django benefited a lot from Python's maturity.