[qmtest] [PATCH] Removing ExtensionClass dependency

[Mark Mitchell]

> The two ideas are compatible.  Suppose we move the dtml library to
> qm.external as Nathaniel suggests, but instead of doing

There are a bunch of things we need to do to make QMTest a "proper"
Python module, including (at least):

(1) Deal with the setup_path.py stuff that adds various things to the
Python search path.  Instead, package things up so that Python can just
find them.

(2) Avoid stomping on existing Python stuff when QMTest is installed.

Nathaniel's patch works on both of these at once, I think:

- 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'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.

I'm also a little bit confused because DTML is already installed in
lib/qm/zope-dtml, so it's not actually going to clash with anything
already installed as far as I can tell.

So, maybe I'm missing the point entirely here?

-- 
Mark Mitchell
CodeSourcery, LLC
mark at codesourcery.com