Having moved from rails to django development the thing I am missing the most is the wide range of mature testing tools in the ruby ecosystem. Django's testing tools feel very primitive comparatively and there's no clear separation of unit, functional and integration tests. I'd agree that in general the python community feels more professional and that the quality of documentation is typically better.

Last I checked out Django they had just added a bunch of features from Rails 1.2. (Edit: sorry, Rails 2.1)

Python suffers from their web framework community being too fragmented, so none of the projects are as mature as Rails.

I use Django for my projects and I don't share this opinion on the maturity aspect. Can you explain your statement a bit more? What aspects of Django are immature?

The release notes for Django 1.4, for example, list support for both Time Zones and Selenium.

Time Zones were added to Rails 2.1 in 2008. selenium-on-rails also debuted in 2008.

Does it not seem strange to you that it took 4 years after Rails for Django to get these features?

There were plenty of extensions that allowed you to use Selenium with Django, I maintained one of them. Django is fairly conservative about including new features into the core that work well as extensions. And this is something I value a lot.

The time zone support, though, was really overdue.

Really, if you wanna complain about something that's in Rails and not in Django properly, talk about database migrations.

South...but I agree that database migrations should be part of the Django core.

Not really a fair feature comparison. If db migration wasn't in Rails, ActiveRecord wouldn't work the way it does. You can't say the same about Django's ORM.

Also, the Django docs is awesome. Nothing gets into master without proper documentation.