[qmtest] PATCH: Enhance DejaGNU result reader

[Mark Mitchell]

Pragnesh Sampat wrote:

> We are using mixed versions, with 2.2 being used on automated systems
> for formal activities and desktops and developers boxes being typically
> more recent with a mix of 2.3.x and 2.4.x.  I think I would be ok moving
> to 2.3 if it is a better solution.

I don't think that 2.2 is bad, per se; I'm just worried about how many
of these things might creep in over time.  The example you found is easy
to fix, with minor obfuscation of the code, using dictionaries, but I
can never remember exactly which versions of Python support exactly
which syntax.  I know that Red Hat 8.0 and RHEL 3 had Python 2.2; RHEL 4
has Python 2.3.

I guess I tend to think sticking with Python 2.2 makes the most sense
for now, even though it would be easier if we could move to 2.3. :-)

-- 
Mark Mitchell
CodeSourcery, LLC
mark at codesourcery.com
(916) 791-8304