XML processing in Python -- changing horses in mid-stream

Tim Rowe digitig at cix.co.uk
Tue Feb 13 19:29:00 CET 2001

The scripts are not very big. The result files could be. The sparse tree 
processing might be the thing.



In article <3a8563ae.3383090887 at news.iol.ie>, sean at digitome.com (Sean Mc 
Grath) wrote:

> Tim,
> How big are the test scripts / test results? If the sizes are
> manageable I would suggest looking at Pyxie Tree processing.
> While processing a tree T, you can create another tree, T1 with
> the results of running the second test script, you can then 
> use the Paste functions to paste the new tree into the
> existing one.
> If size is a problem, you might like to look that the Sparse
> Tree Processing stuff in Pyxie that allows you to switch
> from event processing to tree processing as needed.
> Sean
> On Sat, 10 Feb 2001 14:50 +0000 (GMT Standard Time), digitig at cix.co.uk
> (Tim Rowe) wrote:
> >I have a Python program that parses a test script written in XML and 
> puts >the test results to stdout in XML (with a different DOCTYPE).
> >
> >I also have a Python program that takes the test result XML and 
> processes >it for graphical presentation.
> >
> >Here's my challenge. If the second program were given a test script 
> >instead of results, I would like it to recognise the different 
> doctype, >run the tests and process the results all in one.
> >
> >When my result parser spots a test script I should be able to pass the 
> >script to the test program via a pipe, put the results of the test 
> through >a new result parser, and copy anything relevant from the new 
> result parser >to the old one. But can I stop the old result parser 
> parsing the rest of >the test script?
> >
> >I plan to use either expat or pyxie, whichever is easiest.
> >
> >TIA.
> >
> >

More information about the Python-list mailing list