When RoR was all the rage (the one-true-rage even!) couple of years back, there were a lot of people in the Python world, who were concerned that Ruby might ste

When RoR was all the rage (the one-true-rage even!) couple of years back, there were a lot of people in the Python world, who were concerned that Ruby might steal the thunder from Python. Python people attacked this "problem" in multiple ways. One was the emergence of competing frameworks like Django and Pylons. The other was to work hard on other product lifecycle stories. Some of which were influenced by what was gaining traction elsewhere (automated deployments, TDD). But, some new things also took flight in the Python world, like WSGI, which inspired similar endeavours (Rack, Plack/Perl). Also, Python has better overall ecosystem. You want libraries for obscure (say HVAC) protocol, you have a better chance of finding it in Python, than in Ruby. I think more developers relate to "don't be too clever" attitude taken by python than admitted among this crowd. While RoR was busy redefining the entire Ruby ecosystem in it's own image, Python people were busy building stuff that were truly framework agnostic. Eg: Paste, WSGI, SQLAlchemy, Various templating languages like Jinja2, Mako. Today, it is very easy choose from many competing python frameworks without drinking any one brand of kool-aid.