On 21 January 2003, Andrew Kuchling said:
> Here's the section of documentation I've just written for
> _q_resolve().  Everyone, please suggest clarifications.  (Apologies
> for the RST markup.)

A few minor suggestions...

> ``_q_resolve()`` is only ever called for names that are in
> ``_q_exports`` and that don't already exist in the module or instance.

Suggest change to:

  ... already exist in the containing namespace (module or instance).

> It is not passed the request object, so its return value can't depend
> on the client in any way.  Calls are also memoized; after being called
> the object returned will be added as an attribute of the containing
> module or instance, so ``_q_resolve()`` will be called at most once
  ^^^^^^^^^^^^^^^^^^

*maybe* change to "namespace"

> Let's say this function is in app.ui.  The first time /expensive is
> accessed, _q_resolve('expensive') is called, the
> otherpackage.expensive module is returned and traversal continues.
> app.ui.expensive is also set to the module objects, so future

How about:

  "The imported module is also saved as app.ui.expensive, so ..."

> references to /expensive won't need to invoke the ``_q_resolve()``
> hook.

        Greg