In an attempt to come to some decision on _q_import, here's a summary
of options.

1) Do nothing, and Jon Corbet continues maintaining his patch.

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.

3) Use _q_getname(req, component) instead.  The only change
   required is to call _q_getname() for names that are
   already listed in _q_exports().  This might break some existing
   applications (one occurrence in our application).

Yesterday in a group discussion, I was for 3), but now that the
options are all written out, 2) looks better to me.

MX people: can we have a straw poll to resolve this?

--amk