Comments on: Aspect-oriented Python

Comment by: Hacker’s Guide to Getting in Shape » Aspect-oriented Python and Metaclasses

2009-02-25T09:25:18Z

[...] I came across a nice introductory post on AOP in Python by Dethe Elza titled Aspect-oriented Python. [...]

Comment by: [Python] AoP python « Reading for Life

2009-03-04T06:15:04Z

[...] Aspect-Oriented Python [...]

Comment by: gregturn

2009-03-11T10:32:51Z

I agree that python makes it very easy to plugin things like AOP. In this situation, your AOP advice would be similar to AspectJ, where all instances of a class are wrapped with the advice. I coded an AOP module at http://springpython.webfactional.com/reference/html/aop.html that is based on a) not requiring advice to be applied to all instances and b) being non-intrusive and applicable even if you don’t have access to the original source. I think both of these are valid items any python developer should have.

Comment by: delza

2009-03-11T11:13:56Z

Hi Greg, thanks for the pointer. I intended this as a super-quick overview of the AOP-style features built in to recent versions of Python, so I didn’t explore aspects.py (http://www.cs.tut.fi/~ask/aspects/index.shtml), TransWarp (http://www.zope.org/Members/pje/Wikis/TransWarp/AOPTutorial/view) or its successor, PEAK (http://peak.telecommunity.com/Articles/WhatisPEAK.html). In part because these projects never really seemed to take off, and in part because my own preference is for the lighter, more explicit “AOP-lite” of decorators over the full-on code weaving and join points model. But I agree that both have their place in the toolbox.