I'd like to say that repoze.component ended up being more than just an
entry point for people willing to apply AOP on their apps.
One can easily exercise the pattern of registering components and
looking them up back by just using simple strings rather than defining
interfaces just as markers.
Definitely more straightforward and easy to understand than
zope.component and zope.interface.
Once the concepts are grokked, one can jump into repoze.configuration
and start defining ways to configure repoze.component in a declarative
way using yaml.
Repoze-dev mailing list