Pyramid is actually pretty much a fork of repoze.bfg with some minor changes that allow Pylons developers easier porting. Essentially repoze.bfg were newer than

Pyramid is actually pretty much a fork of repoze.bfg with some minor changes that allow Pylons developers easier porting. Essentially repoze.bfg were newer than Pylons (and therefor learned a lot). It incorporated more flexiblity while being simpler in design. This flexibility also means that a lot of what TurboGears 2 implemented ontop of Pylons isn't needed anymore, Pyramid allows you to use idioms common to both Pylons and TurboGears 2. Additional Pylons were designed as a lot of WSGI middlewares pulled together. Pyramid is not (so much). The repoze.bfg developer so that Pylons developers had already settled on a common configuration of core middleware, and thus made many of the common middlewares required and therefore more tightly integrated. So while Pylons were very much a meta-framework, Pyramid is not as much. I'm unsure about what Turbogears developer exactly wants to do, but there simply isn't as much need for a monolithic framework ontop of Pyramid since it itself is somewhat monolithic and flexible enough to allow extension through libraries. Instead what probably will happen is that a lot of all the extra libraries already built as part of Turbogears 2 will be reworked to work as libaries for Pyramid (not on top of it). (but all of the is conjecture) Note. I follow the mail-list much don't really participate in the development of any of these projects.