[qmtest] PATCH: Enhance DejaGNU result reader

[Pragnesh Sampat]

On Tue, 2005-10-25 at 13:28 -0700, Mark Mitchell wrote:
> 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.

Red Hat 9.0 has 2.2, which is where I ran into the issue.  I have also
occasionally run into things where I needed to something different for
python 2.2, after I check in, since most of the systems that I use have
2.3 or later and I would miss something locally and get caught later. 
It is getting harder to keep track of these little things.

> 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. :-)

You are probably probably right.  Many of the newer features are nice
(I find the "What's New in Python 2.x" pages on python.org very
useful), but I have not had a compelling case yet where something
trumped compatibility.  Bound to happen one of these days soon, I think.

-Pragnesh