* Mike Orr wrote on [2007-05-01 12:48:03 -0700]:
>  You can make a utility script like this:
-- snip --
>  Import hooks are fragile in Python, and often break when combined with
>  import hooks from other packages.

Can't speak for the developers of QP but no doubt this was one of
the reasons behind dropping the import hook in Quixote's cousin QP
in favour of putting two lines in one or more of a package's
__init__.py:

    from qpy.compile import compile_qpy_files
    compile_qpy_files(__path__[0])

If you have a project hierarchy that looks something like this:

    ../someproj/
        __init__.py
        object1.py
        object2.py
        ui/
            __init__.py         < include compile
            object1.qpy
            object2.qpy
            form/
                __init__.py     < include compile
                widget.qpy

Having been bit by the SQLObject/Quixote PTL import hook issue in
the past, I don't mind adding two lines of code in one or two
__init__.py files per project to avoid the hassle.

PTL files can be used as QPY files generally without any
modifications other than a file rename.

Never done this but I presume there is nothing stopping one from
using QPY in Quixote. Drop the PTL import hook, rename files, modify
your __init__.py as described, and that might be that.

To the original poster, perhaps that's a less onerous way of moving
forward than learning Turbogears (Quixote + QPY, or QP+QPY - either
route has less relearning involved).

See QPY:
http://www.mems-exchange.org/software/

Mike