I don't know where you are getting the idea that Django's community is more than marginally smaller than Rails'. Google Trends, StackOverflow questions, number

I don't know where you are getting the idea that Django's community is more than marginally smaller than Rails'. Google Trends, StackOverflow questions, number of GitHub projects, average followers/forks for popular Django/Rails extensions, number/popularity of significant sites built with each, and the number of stories I see pop-up on sites like HN for each framework are all relatively equivalent. Django for AppEngine is barely a variant, it's just a different handler for the ORM to interact with the non-relational backend. Jinja's a template engine that you can plug-in on top of Django if you want (like if you wanted to use HAML instead of ERB). Plenty of Django devs choose Tornado for their COMET needs (I know of almost no one that uses it as their entire web stack). Flask and Bottle are nice micro-frameworks, but aren't well-suited at all for large sites unless you feel like doing a lot of extra work yourself. Jekyll isn't a Python project, it's Ruby's static site generator (but does have a Python port called Hyde). Pylons (now Pyramid) is the only significant contender to Django. Think of it as Sinatra's market-share compared to Rails. So when you actually compare the two, Python has no more "framework fragmentation" than Ruby. To someone outside of the community just listing off frameworks that they found on Google, sure it might seem that way.