While reading about all the emerging web application frameworks for Python I keep getting the feeling that they're converging on (and meanwhile reinventing) Zope 3. Not to say that each doesn't have its strong points and original innovations, it's just that the vast majority of the groundwork has already been done, why keep doing it again?

It seems that I'm not the only one with similar feelings:

One final thought for today about the new wave of Python web frameworks: I really can't understand why Zope 3 seems to be entirely ignored in this respect. Zope 3 is a framework that was carefully developed taking into account the many lessons learned from Zope, which is without a doubt the most successful Python web framework to date. Zope 2 managed to get a reputation as an unpythonic framework, so maybe Zope 3, even with its painstakingly designed component architecture, is paying for it. Or perhaps there's a lack of influential bloggers touting it as the next big thing (Rails anyone?) or the project's web page is so terrible that few people think it's worth checking out. Whatever the reason, I think Zope 3 should be taken into account when exploring web frameworks of the future, so I intend to look into this matter more thoroughly. -- Carlos de la Guardia

So, can anyone tell me why they don't like/don't know about/are afraid of Zope 3?