I suspect its because Pylons has only relatively recently reached a stage where the code and documentation makes it simple enough to dive in and do great things

I suspect its because Pylons has only relatively recently reached a stage where the code and documentation makes it simple enough to dive in and do great things without too much hassle. I think Pylons has broader and deeper goals, so there has been a period of ramping up and getting the foundations in place, while the efforts put into Django's development have been focused on making specific things easy. Now Pylons is settling down and maturing, it will probably start to become much more widely used and appreciated. Also, Pylons may benefit from Django's recent boost in a similar way the link suggests Django is benefiting from Rails.