Fri, 30 Jun 2000 06:23:09 +0100
At 05:22 PM 6/29/00 -0500, Paul Prescod wrote:
>Sean McGrath wrote:
>> The common thread is the PYX notation. Pyxie is a library
>> that is based on manipulating the notation.
>I still don't understand.
>You just said that Pyxie can work directly from the output of pyexat.
Yes. Internally, in order to avoid the unnecessary overhead
of forking a subprocess, Pyxie uses Pyexpat to parse
XML and create a PYX stream.
>seems that you could have a perfectly useful Pyxie app that doesn't use
No. The tree builder and event dispatcher need to be fed
data in PYX notation. How you get the PYX data stream
is up to you. For example, you could generate PYX from
an Access database using COM and feed it to the event
? And a perfectly useful PYX app that doesn't use Pyxie (or
>Python at all).
Yes. This part is true. For example, this is from
pyx <xmlfile> | grep ^- | perl -pe 's/^-//; s/\\n\n//;' | diction
>Perhaps you could expand on your statement that Pyxie is for
>"manipulating the notation." Does pyxie always use pyx as
> a) input
> b) output
> c) internal data structure
Pyxie uses PYX as input. It can generate PYX as output more
more typically will generate XML as output. PYX is not
used as an internal data structure.
I hope this clarifies matters.
XML Processing With Python
ISBN: 0 13 021119 2