Jason E. Sibre wrote:

> 2. "None has no _q_exports list"...  None?  That's odd, and with the
> absolute path implied by "from qxdemo.ui import foo", when you're in
> qxdemo.ui... Could this be a result of an import loop/deadlock?  I don't
> know.  I haven't had any problems with that in a quite a while (since I
> first started with Qx and learned how NOT to arrange my packages!), and I've
> forgotten the symptoms.  I don't think you can get yourself in a loop that
> easily, though.
>
> I will say, "You don't need that import in step 2."

Jason's right, and I'm to blame for passing that on. If you're in a
package (__init__.py), you don't have to import the names of modules in
your package, you can just add them to _q_exports. Explicitly importing
all modules is a habit of mine in Quixote, but it's arguably a bad one
if it might introduce import errors...

> Keep us posted!
>
> Jason

+1 on that!

-- Graham