In the Python community, whenever discussing web development, there is always the elephant in the room: Zope. The granddaddy of the web frameworks. Often thought of as something to be avoided at all costs, Zope is little discussed.
Which is interesting, considering that one of the more discussed (perhaps not the most; that award is probably taken by Django, and second place most likely by Flask) modern Python web frameworks, Pyramid, can trace its lineage directly back to Zope (and, indeed, the number of zope.* packages it uses is nonzero).
It’s pretty much accepted in many circles at this point that Zope is essentially “a bad word”; a failure; a complex mess, with no remaining lessons to give; essentially, with no remaining redeeming value making it worthy of consideration.
This is a great shame; Zope has a lot to teach
