> > Do you think I ought parse the workspace XML file [not using Gumpy > > classes], and extract all info from there? > > If all information you need is in there anyway, I'd say yes. > Otherwise the two sets of configurations would soon run out of sync.
If it isn't all there, it probably should be. I agree, read the workspace. I found a simple DOM parser in Python that allowed me to set variables from attribute values, so I could extract basedir and such from the workspace. It also extracts mail stuff (added w/ Gumpy) so it can mail failed logs to the owner. I don't think it needs much more. The replacement for gumpy.bat|sh is coming along, although I'm not quite ready to switch LSD to it. It needs to clean *.pyc (important for when Gumpy get's refactored between runs) and it needs [IMHO] to copy forrest output (for days when that fails) but then I think it'll be ready. (As CVS logs no doubt showed, I got distracted from this 'cos of the desire to make Gumpy more portable, and remove cat/ls usage.) regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
