[qmtest] [PATCH] Removing ExtensionClass dependency

[Zack Weinberg]

Mark Mitchell <mark at codesourcery.com> writes:

> - The bits that change the import statements in DTML where Nathaniel has
> "subltety" comments are (I think) trying to work on (1).  (Because
> Nathaniel moved things to "external", because that directory didn't get
> added to the Python path by setup_path.py.)  But maybe I misunderstand?
>
> - Moving things to qm.external so that installing QMTest in the "usual
> place", where DTML is already installed, works out OK.

I am not sure, perhaps you'd better clarify, Nathaniel?

> I'd rather have a clear plan before we dive in here.  It seems
> reasonable to deal with (2) without dealing with (1) first, to me.
>
> I guess you're thinking about how to make a GNU/Linux binary package
> that works *whether or not* DTML is already installed.  I'm wondering if
> we need to deal with that complexity, or if we can just have two binary
> packages: one that contains DTML and one that expects you've already got
> it installed.

It seemed easier to do it that way than the way you're suggesting,
honestly.  The only other way I see short of having web.py edited at
install time, is to put qm.external on the python path - which may
make sense.

zw