This looks very interesting, Phillip. I haven't downloaded the package yet, but I read the wiki and it finally made sense once I understood the goal (I think): TW lets you set up the class inheritance hierarchy at runtime. In normal OO methodology, you can only extend classes. With TW, you can also slip your own version of a base class into a class hierarchy (without actually modifying the Python class hierarchy, of course.) What is your vision of integrating AOP into a persistent object system? Would one drop in an object that modifies the class loading mechanism so that the classes come from a TW component rather than Python modules? Shane "Phillip J. Eby" wrote:
It's here... the first preview release of TransWarp. The bad news is, it only contains working versions of the aspect-oriented programming tools (the rest of the package is in flux). The good news is:
1. It's a *robust* working version, with 114 unit tests to prove it, and
2. There's state-of-the-art documentation, including such cutting-edge technology as tutorials, and super-simple examples. :)
You can find the software at:
http://www.zope.org/Members/pje/TransWarp/
and the online documentation at:
http://www.zope.org/Members/pje/Wikis/TransWarp/
Comments welcome. Enjoy.