Need a compelling argument to use Django instead of Rails

[John J. Lee]

Steve Holden <steve at holdenweb.com> writes:
[...]
> Well, my view is that both are frameworks, and so you will inevitably 
> "run out of steam" at some point if your implementation plans become too 
> ambitious. The impression I get is that Rails is relatively inflexible 
> on database schemas, and once you get "off the beaten track" it gets 
> difficult to cope with complex existing databases.

I get that overall impression of Django too (as being more tightly
coupled to itself, hence less flexible, when compared with TurboGears
in particular).  I haven't done much with it yet, though (and
presumably the 'magic-removal' branch landing did some good).

What do you make of the rest of Django (aside from the DB stuff)?

It's a shame TurboGears doesn't yet have a solid "out of the box" CRUD
admin interface as Django.


John