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.