-> > 2) Add _q_import(component) (_q_resolve, _q_bind_name, whatever),
-> >    which takes the string component and return a matching object.
-> >
-> >   2b) This may also do setattr(container, component, object),
-> >       so future accesses don't go through _q_import() at all.
->
-> Either of these is fine by me.  I have nothing against the concept, and
-> I *think* _q_import() is an OK name.  I can definitely see Jon's need
-> for it (or at least, I did the last time this was discussed and Jon
-> explained his need in detail).  But I have no burning need for it
-> myself.

#2 is fine by me.  No burning need, but I'm sure I'll figure out a
way to use it to do some mildly clever hack, which is what programming
is all about, right? ;)

--t