From larsga at ontopia.net  Tue Nov  1 00:14:06 2005
From: larsga at ontopia.net (Lars Marius Garshol)
Date: Tue, 01 Nov 2005 00:14:06 +0100
Subject: [XML-SIG] "borrowing" one of your modules
In-Reply-To: <5.2.0.9.2.20051031114244.02799408@mailserv.uic.edu>
References: <5.2.0.9.2.20051031114244.02799408@mailserv.uic.edu>
Message-ID: <m3fyqhs2ip.fsf@ontopia.net>


* Alex Neyfakh
|
| I would like to request your permission to "borrow" one of the
| modules (DTDparser.py) from your PyXML package that we would like to
| include into our software after making some modifications to it. Our
| software is being written purely for research purposes and will be
| available for free download. We plan to acknowledge the origin of
| the module in its docstring.  Is this OK with you?

I assume this is the dtdparser.py module that's part of the xmlproc
parser? If so, that's OK with me. (I'm the original author, although
Martin von L?wis has since made significant contributions.)

-- 
Lars Marius Garshol, Ontopian         <URL: http://www.ontopia.net >
GSM: +47 98 21 55 50                  <URL: http://www.garshol.priv.no >


From Alain.Desilets at nrc-cnrc.gc.ca  Wed Nov  2 21:06:05 2005
From: Alain.Desilets at nrc-cnrc.gc.ca (Desilets, Alain)
Date: Wed, 2 Nov 2005 15:06:05 -0500
Subject: [XML-SIG] Unicode XML
Message-ID: <E4D07AB09F5F044299333C8D0FEB45E9BB0CBC@nrccenexb1.nrc.ca>

I have an application which uses a WDDXMarshaller (the marshaller
variable below), to encode a dictionary (the mess_argvals variable) as
an XML string, as follows:

marshaller.dumps(mess_argvals)


My problem is that the dictionary mess_argvals may contain some values
which are strings with unicode characters in them. But unfortunately,
dumps() generates XML code that uses the default encoding, i.e. the XML
string starts with:

<?xml version="1.0" ?>

How can I make dumps() generate XML that uses the UTF-8 encoding. In
other words, how do I tell it to generate XML that starts with this
line:

<?xml version="1.0" encoding="UTF-8" ?>

From fredrik at pythonware.com  Wed Nov  2 21:14:44 2005
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Wed, 2 Nov 2005 21:14:44 +0100
Subject: [XML-SIG] Unicode XML
References: <E4D07AB09F5F044299333C8D0FEB45E9BB0CBC@nrccenexb1.nrc.ca>
Message-ID: <dkb6nf$njm$1@sea.gmane.org>

"Desilets, Alain" wrote:

> My problem is that the dictionary mess_argvals may contain some values
> which are strings with unicode characters in them. But unfortunately,
> dumps() generates XML code that uses the default encoding, i.e. the XML
> string starts with:
>
> <?xml version="1.0" ?>
>
> How can I make dumps() generate XML that uses the UTF-8 encoding. In
> other words, how do I tell it to generate XML that starts with this
> line:
>
> <?xml version="1.0" encoding="UTF-8" ?>

utf-8 is the default encoding for XML, so that encoding declaration is optional.

</F> 




From jeremy.kloth at fourthought.com  Wed Nov  2 21:22:11 2005
From: jeremy.kloth at fourthought.com (Jeremy Kloth)
Date: Wed, 2 Nov 2005 14:22:11 -0600
Subject: [XML-SIG] Unicode XML
In-Reply-To: <E4D07AB09F5F044299333C8D0FEB45E9BB0CBC@nrccenexb1.nrc.ca>
References: <E4D07AB09F5F044299333C8D0FEB45E9BB0CBC@nrccenexb1.nrc.ca>
Message-ID: <200511021322.11670.jeremy.kloth@fourthought.com>

On Wednesday 02 November 2005 1:06 pm, Desilets, Alain wrote:
> I have an application which uses a WDDXMarshaller (the marshaller
> variable below), to encode a dictionary (the mess_argvals variable) as
> an XML string, as follows:
>
> marshaller.dumps(mess_argvals)
>
>
> My problem is that the dictionary mess_argvals may contain some values
> which are strings with unicode characters in them. But unfortunately,
> dumps() generates XML code that uses the default encoding, i.e. the XML
> string starts with:
>
> <?xml version="1.0" ?>
>
> How can I make dumps() generate XML that uses the UTF-8 encoding. In
> other words, how do I tell it to generate XML that starts with this
> line:
>
> <?xml version="1.0" encoding="UTF-8" ?>

These two XML declarations are equivalent.  The default encoding for XML is 
UTF-8.

Is your problem that you are getting an exception in the dumps() call?

-- 
Jeremy Kloth
Fourthought, Inc.
http://fourthought.com/
http://4suite.org/

From stephane at sources.org  Wed Nov  2 22:25:09 2005
From: stephane at sources.org (Stephane Bortzmeyer)
Date: Wed, 2 Nov 2005 22:25:09 +0100
Subject: [XML-SIG] Unicode XML
In-Reply-To: <E4D07AB09F5F044299333C8D0FEB45E9BB0CBC@nrccenexb1.nrc.ca>
References: <E4D07AB09F5F044299333C8D0FEB45E9BB0CBC@nrccenexb1.nrc.ca>
Message-ID: <20051102212509.GA19728@sources.org>

On Wed, Nov 02, 2005 at 03:06:05PM -0500,
 Desilets, Alain <Alain.Desilets at nrc-cnrc.gc.ca> wrote 
 a message of 22 lines which said:

> But unfortunately,
> dumps() generates XML code that uses the default encoding, i.e. the XML
> string starts with:
> 
> <?xml version="1.0" ?>
> 
> How can I make dumps() generate XML that uses the UTF-8 encoding. 

Why? UTF-8 is the default, it seems. 

http://www.w3.org/TR/2004/REC-xml-20040204/

2.8 Prolog and Document Type Declaration

In the absence of information provided by an external transport
protocol (e.g. HTTP or MIME), it is a fatal error for an entity
including an encoding declaration to be presented to the XML processor
in an encoding other than that named in the declaration, or for an
entity which begins with neither a Byte Order Mark nor an encoding
declaration to use an encoding other than UTF-8. Note that since ASCII
is a subset of UTF-8, ordinary ASCII entities do not strictly need an
encoding declaration.

From python-xml at jonc.me.uk  Thu Nov  3 12:51:17 2005
From: python-xml at jonc.me.uk (Jonathan Cooper)
Date: Thu, 3 Nov 2005 11:51:17 +0000
Subject: [XML-SIG] RELAX NG and Python
Message-ID: <20051103115117.GA12644@finarfin.cooper.xfnet>

I'm having some difficulties validating using RELAX NG in Python.  I've
been writing a schema for CellML files (www.cellml.org; current schema is
at http://jonc.me.uk/stuff/cellml1.0.rng), and I can validate various
example documents using jing.  The python tools I've come across have not
been as successful.


4Suite appears to have problems parsing constructs like:
foreign-elements =
  element * - (cellml:* | rdf:* | mathml:*) { foreign-nodes }*

It throws an RngSchemaInvalidException: Unamed Element


Using lxml results in an error value of XML_RELAXNG_ERR_MEMORY, which
isn't very helpful.


Using the libxml2 module directly says that the file is invalid (curious,
since jing says it's valid when using the same schema, and it looks fine
to me).  Trying to find out which element 'fails' is tricky, since
calling LineNumber() on the xmlTextReaderLocator object passed to my
error handler causes a segfault :(


Any suggestions for what to try next?

TIA,
 Jonathan.

-- 
Jonathan Cooper      MSN: msn at jonc.me.uk      www: jonc.me.uk/

In democracy your vote counts. In feudalism your count votes.

From veillard at redhat.com  Thu Nov  3 14:39:56 2005
From: veillard at redhat.com (Daniel Veillard)
Date: Thu, 3 Nov 2005 08:39:56 -0500
Subject: [XML-SIG] RELAX NG and Python
In-Reply-To: <20051103115117.GA12644@finarfin.cooper.xfnet>
References: <20051103115117.GA12644@finarfin.cooper.xfnet>
Message-ID: <20051103133956.GB896@redhat.com>

On Thu, Nov 03, 2005 at 11:51:17AM +0000, Jonathan Cooper wrote:
> Using the libxml2 module directly says that the file is invalid (curious,
> since jing says it's valid when using the same schema, and it looks fine
> to me).  Trying to find out which element 'fails' is tricky, since
> calling LineNumber() on the xmlTextReaderLocator object passed to my
> error handler causes a segfault :(

  Ranting here about libxml2 is fine, but is garanteed to have no effect
whatsoever.

  If you have bugs to reports, that's the way:
    http://xmlsoft.org/bugs.html
I didn't know locator were even provided at the Python level I have no idea
what you did.
Using the reader to validate RNG may introduce difficulties.
What does xmllint --relaxng foo.rng foo.xml says ?

  And don't report this here, either on bugzilla or on the libxml2
mailing-list, follow the steps explained on that page if you want to see
progresses.

Daniel


-- 
Daniel Veillard      | Red Hat http://redhat.com/
veillard at redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

From noreply at sourceforge.net  Thu Nov  3 22:14:24 2005
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 03 Nov 2005 13:14:24 -0800
Subject: [XML-SIG] [ pyxml-Bugs-1347683 ] PrettyPrint eats some PCDATA
	elements
Message-ID: <E1EXmPg-0002pQ-KT@sc8-sf-web4.sourceforge.net>

Bugs item #1347683, was opened at 2005-11-03 13:11
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=1347683&group_id=6473

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Wilfredo Sanchez (wsanchez)
Assigned to: Nobody/Anonymous (nobody)
Summary: PrettyPrint eats some PCDATA elements

Initial Comment:
PrettyPrint(doc) omits PCDATA elements that contain only "\n".  
Print(doc) does not do this.

Test script attached.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=1347683&group_id=6473

From noreply at sourceforge.net  Thu Nov 10 00:10:17 2005
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 09 Nov 2005 15:10:17 -0800
Subject: [XML-SIG] [ pyxml-Bugs-1352653 ] Pretty printing not working
Message-ID: <E1EZz57-0003lp-FN@sc8-sf-web2.sourceforge.net>

Bugs item #1352653, was opened at 2005-11-09 23:10
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=1352653&group_id=6473

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Fabian Sturm (sturmf)
Assigned to: Nobody/Anonymous (nobody)
Summary: Pretty printing not working

Initial Comment:
Hi!

I try to get pretty printing working with xml.sax.writer.
Unfortunately I failed.

this is teh code I used:

#!/usr/bin/python

import sys
import string
import xml.sax.writer

d = 'somthing'

w = xml.sax.writer.PrettyPrinter(sys.stdout)

w.startDocument()

w.startElement('test', {})

w.startElement('test2', {})
w.characters(d, 0, len(d))
w.endElement('test2')

w.endElement('test')


w.endDocument()

The output is:
<?xml version="1.0" encoding="iso-8859-1"?>
<test><test2>somthing</test2></test>

and the expected output is (or similar):
<?xml version="1.0" encoding="iso-8859-1"?>
<test>
  <test2>somthing</test2>
</test>

Any help would be great!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=1352653&group_id=6473

From lfurlong at imim.es  Thu Nov 10 14:32:22 2005
From: lfurlong at imim.es (FURLONG -, LAURA INES)
Date: Thu, 10 Nov 2005 14:32:22 +0100
Subject: [XML-SIG] xml.sax._exceptions.SAXParseException
Message-ID: <66373AD054447F47851FCC5EB49B3611CD10DC@basquet.imim.es>

Hi,


When I try to parse an xml file I get the following error:


 File "<stdin>", line 1, in ?
  File "/usr/lib/python2.3/site-packages/_xmlplus/sax/expatreader.py", line 109, in parse
    xmlreader.IncrementalParser.parse(self, source)
  File "/usr/lib/python2.3/site-packages/_xmlplus/sax/xmlreader.py", line 125, in parse
    self.close()
  File "/usr/lib/python2.3/site-packages/_xmlplus/sax/expatreader.py", line 226, in close
    self.feed("", isFinal = 1)
  File "/usr/lib/python2.3/site-packages/_xmlplus/sax/expatreader.py", line 220, in feed
    self._err_handler.fatalError(exc)
  File "/usr/lib/python2.3/site-packages/_xmlplus/sax/handler.py", line 38, in fatalError
    raise exception
xml.sax._exceptions.SAXParseException: <unknown>:4298:10: unclosed token

but the xml file looks ok, it can be visualized in a web browser without any problem. Does anybody know what is going on?

Thanks,


Laura Furlong


From mike at skew.org  Thu Nov 10 20:38:32 2005
From: mike at skew.org (Mike Brown)
Date: Thu, 10 Nov 2005 12:38:32 -0700 (MST)
Subject: [XML-SIG] xml.sax._exceptions.SAXParseException
In-Reply-To: <66373AD054447F47851FCC5EB49B3611CD10DC@basquet.imim.es>
Message-ID: <200511101938.jAAJcWVd087335@chilled.skew.org>

FURLONG -, LAURA INES wrote:
> When I try to parse an xml file I get the following error:
> 
> 
>  File "<stdin>", line 1, in ?
>   File "/usr/lib/python2.3/site-packages/_xmlplus/sax/expatreader.py", line 109, in parse
>     xmlreader.IncrementalParser.parse(self, source)
>   File "/usr/lib/python2.3/site-packages/_xmlplus/sax/xmlreader.py", line 125, in parse
>     self.close()
>   File "/usr/lib/python2.3/site-packages/_xmlplus/sax/expatreader.py", line 226, in close
>     self.feed("", isFinal = 1)
>   File "/usr/lib/python2.3/site-packages/_xmlplus/sax/expatreader.py", line 220, in feed
>     self._err_handler.fatalError(exc)
>   File "/usr/lib/python2.3/site-packages/_xmlplus/sax/handler.py", line 38, in fatalError
>     raise exception
> xml.sax._exceptions.SAXParseException: <unknown>:4298:10: unclosed token
> 
> but the xml file looks ok, it can be visualized in a web browser without any problem. Does anybody know what is going on?

Which version of PyXML do you have installed?
How are you parsing the file? (let's see the Python code)
Can you point us to the XML file?

From guido at python.org  Fri Nov 11 04:53:41 2005
From: guido at python.org (Guido van Rossum)
Date: Thu, 10 Nov 2005 19:53:41 -0800
Subject: [XML-SIG] New XML module
Message-ID: <ca471dc20511101953ve850477uc73b57a2f25c4a48@mail.gmail.com>

At Elemental I've had a lot of success with a simple module that
converts between Python data structures and XML. I mentioned this code
in a talk at EuroPython this summer and there was quite a bit of
interest in it (despite my emphasis on its limitations).

Encouraged by that interest I'm contributing the code to the PSF for
possible inclusion in the Python standard library. The first step of
contribution is to put it up on the SF tracker:

https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1337648&group_id=5470

Since I'm not all that plugged into the Python XML community I'd like
to get some feedback on the code (I've subscribed to this list
specifically for that purpose).

A quick plug is the little test method included at the end of the code:

def _test():
    class Inner(ElementClass):
        __element__ = "inner"
        __attributes__ = {"special": Boolean}
        __characters__ = "text"
    class Outer(ElementClass):
        __element__ = "outer"
        __attributes__ = {"id": Integer, "name": String}
        __children__ = {Inner: "inner[]"}
    sample = '''<outer id="1" name="foo">
        <inner special="false">blah, blah</inner>
    </outer>'''
    outie = Outer.__parseText__(sample)
    print (outie.id, outie.name)
    for innie in outie.inner:
        print (innie.special, innie.text, str(innie))
    print outie

The output from running this is:

(1, 'foo')
(False, 'blah, blah', '<inner special="false">blah, blah</inner>')
<outer
    id="1"
    name="foo">
  <inner special="false">blah, blah</inner>
</outer>

--Guido van Rossum (home page: http://www.python.org/~guido/)

From lfurlong at imim.es  Fri Nov 11 11:15:26 2005
From: lfurlong at imim.es (FURLONG -, LAURA INES)
Date: Fri, 11 Nov 2005 11:15:26 +0100
Subject: [XML-SIG] xml.sax._exceptions.SAXParseException
Message-ID: <66373AD054447F47851FCC5EB49B3611CD10E0@basquet.imim.es>

Mike,

Thank you very much for your quick response. So quick that I have just realized that the problem is not in the parser but in the file! I download it from the NCBI web site, and it seems to be (sometimes) a problem during the download process resulting in a file that is not complete and therefore not well-formed. I have solved the problem checking first that the file downloaded is ok and then proceeded with the xml parsing.

Cheers!

Laura



-----Original Message-----
From: Mike Brown [mailto:mike at skew.org]
Sent: Thu 11/10/2005 8:38 PM
To: FURLONG -, LAURA INES
Cc: xml-sig at python.org
Subject: Re: [XML-SIG] xml.sax._exceptions.SAXParseException
 
FURLONG -, LAURA INES wrote:
> When I try to parse an xml file I get the following error:
> 
> 
>  File "<stdin>", line 1, in ?
>   File "/usr/lib/python2.3/site-packages/_xmlplus/sax/expatreader.py", line 109, in parse
>     xmlreader.IncrementalParser.parse(self, source)
>   File "/usr/lib/python2.3/site-packages/_xmlplus/sax/xmlreader.py", line 125, in parse
>     self.close()
>   File "/usr/lib/python2.3/site-packages/_xmlplus/sax/expatreader.py", line 226, in close
>     self.feed("", isFinal = 1)
>   File "/usr/lib/python2.3/site-packages/_xmlplus/sax/expatreader.py", line 220, in feed
>     self._err_handler.fatalError(exc)
>   File "/usr/lib/python2.3/site-packages/_xmlplus/sax/handler.py", line 38, in fatalError
>     raise exception
> xml.sax._exceptions.SAXParseException: <unknown>:4298:10: unclosed token
> 
> but the xml file looks ok, it can be visualized in a web browser without any problem. Does anybody know what is going on?

Which version of PyXML do you have installed?
How are you parsing the file? (let's see the Python code)
Can you point us to the XML file?


From Uche.Ogbuji at fourthought.com  Fri Nov 11 21:05:49 2005
From: Uche.Ogbuji at fourthought.com (Uche Ogbuji)
Date: Fri, 11 Nov 2005 13:05:49 -0700
Subject: [XML-SIG] New XML module
In-Reply-To: <ca471dc20511101953ve850477uc73b57a2f25c4a48@mail.gmail.com>
References: <ca471dc20511101953ve850477uc73b57a2f25c4a48@mail.gmail.com>
Message-ID: <1131739549.5807.160.camel@borgia>

On Thu, 2005-11-10 at 19:53 -0800, Guido van Rossum wrote:
> At Elemental I've had a lot of success with a simple module that
> converts between Python data structures and XML. I mentioned this code
> in a talk at EuroPython this summer and there was quite a bit of
> interest in it (despite my emphasis on its limitations).
> 
> Encouraged by that interest I'm contributing the code to the PSF for
> possible inclusion in the Python standard library. The first step of
> contribution is to put it up on the SF tracker:
> 
> https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1337648&group_id=5470
> 
> Since I'm not all that plugged into the Python XML community I'd like
> to get some feedback on the code (I've subscribed to this list
> specifically for that purpose).
> 
> A quick plug is the little test method included at the end of the code:
> 
> def _test():
>     class Inner(ElementClass):
>         __element__ = "inner"
>         __attributes__ = {"special": Boolean}
>         __characters__ = "text"
>     class Outer(ElementClass):
>         __element__ = "outer"
>         __attributes__ = {"id": Integer, "name": String}
>         __children__ = {Inner: "inner[]"}
>     sample = '''<outer id="1" name="foo">
>         <inner special="false">blah, blah</inner>
>     </outer>'''
>     outie = Outer.__parseText__(sample)
>     print (outie.id, outie.name)
>     for innie in outie.inner:
>         print (innie.special, innie.text, str(innie))
>     print outie
> 
> The output from running this is:
> 
> (1, 'foo')
> (False, 'blah, blah', '<inner special="false">blah, blah</inner>')
> <outer
>     id="1"
>     name="foo">
>   <inner special="false">blah, blah</inner>
> </outer>

Feels a bit like XIST.  Is the class def per element type mandatory?  If
not, what do defaults look like?

For my part, I think that there are so many XML processing idioms based
on user preference that I'd balk at blessing any one.  In retrospect I
think it was a mistake to even bless SAX and DOM by putting them in the
stdlib.  I think that XML processing is parallel to Web frameworks in
this respect.  I suppose an equivalent of BaseHTTPServer makes sense,
but IMO minidom, SAX and pulldom already serve for that.

Nevertheless, I've been looking forward to seeing this module of yours
for a while and I'll try to test it out and provide some feedback.


-- 
Uche Ogbuji                               Fourthought, Inc.
http://uche.ogbuji.net                    http://fourthought.com
http://copia.ogbuji.net                   http://4Suite.org
Articles: http://uche.ogbuji.net/tech/publications/


From rsalz at us.ibm.com  Fri Nov 11 22:21:05 2005
From: rsalz at us.ibm.com (Richard Salz)
Date: Fri, 11 Nov 2005 15:21:05 -0600
Subject: [XML-SIG] New XML module
In-Reply-To: <1131739549.5807.160.camel@borgia>
Message-ID: <OF4A0E5E86.EC3C880F-ON852570B6.0072401D-852570B6.0075685A@us.ibm.com>

> In retrospect I
> think it was a mistake to even bless SAX and DOM by putting them in the
> stdlib.

On the one hand I agree with this -- why should these pigs be better than 
any other animals on the farm -- but on the other hand, as someone who 
wants to build higher-level facilities on top of XML, it's a real pain. 
"The nice thing about standards is that there's so many to choose from" 
was a complaint, not praise, and string.replace('standards', 'doms') does 
not make it any better.

        /r$

-- 
SOA Appliance Group
IBM Application Integration Middleware


From uche.ogbuji at fourthought.com  Fri Nov 11 22:48:10 2005
From: uche.ogbuji at fourthought.com (Uche Ogbuji)
Date: Fri, 11 Nov 2005 14:48:10 -0700
Subject: [XML-SIG] New XML module
In-Reply-To: <OF4A0E5E86.EC3C880F-ON852570B6.0072401D-852570B6.0075685A@us.ibm.com>
References: <OF4A0E5E86.EC3C880F-ON852570B6.0072401D-852570B6.0075685A@us.ibm.com>
Message-ID: <1131745690.5807.183.camel@borgia>

On Fri, 2005-11-11 at 15:21 -0600, Richard Salz wrote:
> > In retrospect I
> > think it was a mistake to even bless SAX and DOM by putting them in the
> > stdlib.
> 
> On the one hand I agree with this -- why should these pigs be better than 
> any other animals on the farm -- but on the other hand, as someone who 
> wants to build higher-level facilities on top of XML, it's a real pain. 
> "The nice thing about standards is that there's so many to choose from" 
> was a complaint, not praise, and string.replace('standards', 'doms') does 
> not make it any better.

Well WXS was supposed to be the one schema standard to choose from,
right? ;-)  I also wonder how many people will accept XQuery as the
default way to access collections of XML.

But taking tongue out of cheek, I think my problem with your point lies
in "string.replace('standards', 'doms')".  I'm quite fine with the idea
of minidom as the Python standard DOM (even though I prefer our own
Domlette).  But this is not a matter of blessing one of many DOMs, it's
a matter of blessing one of many processing idioms entirely.  DOM is but
one class.  Here is a categorization I've used:

A. Python DOMs: minidom, Domlete, pxdom, etc.
B. Python Infosets: ElementTree, pyRXPu, etc.
C. XML-schema-driven data bindings: GenerateDS, etc.
D. Python-schema-driven data bindings: XIST, Guido's module (I think),
etc.
E. Non-schema-driven data bindings: Amara bindery, xmltramp, Gnosis,
etc.
F. Call-back stream APIs: SAX, PyExpat, etc.
G. Iterator stream APIs: ElementTree iterparse, Amara pushbind, pulldom,
etc.

Python's stdlib currently blesses one from A, two from F and one from G.
Guido's proposal would add one from D.  I suppose one could argue that
it's OK to have one from each category, but I say that would just
confuse the heck out of users.  One could argue that even having 5
entries would confuse the heck out of users.  Or is that no worse
confusion than having two dozen viable third-party options?  I don't
know.

I do know one thing:  I can think of situations where I would prefer
each of A through G.  Some idioms really are better than others for some
tasks.  XML is incredibly diverse, and I think it's very hard to pick
one-size-fits-all solutions.  That's the main concern that gives me
pause.


-- 
Uche Ogbuji                               Fourthought, Inc.
http://uche.ogbuji.net                    http://fourthought.com
http://copia.ogbuji.net                   http://4Suite.org
Articles: http://uche.ogbuji.net/tech/publications/


From rsalz at us.ibm.com  Sat Nov 12 05:27:52 2005
From: rsalz at us.ibm.com (Richard Salz)
Date: Fri, 11 Nov 2005 23:27:52 -0500
Subject: [XML-SIG] New XML module
In-Reply-To: <1131745690.5807.183.camel@borgia>
Message-ID: <OFAD78A368.F4D5AAB5-ON852570B7.00185B26-852570B7.0018A472@us.ibm.com>

I like your categorizations.

I don't really have any solution to propose; I'm just pointing out that 
the current situation makes it hard to develop a "next layer" of XML 
toolkits.
        /r$
-- 
SOA Appliance Group
IBM Application Integration Middleware



From walter at livinglogic.de  Mon Nov 14 10:16:52 2005
From: walter at livinglogic.de (=?iso-8859-1?Q?Walter_D=F6rwald?=)
Date: Mon, 14 Nov 2005 10:16:52 +0100 (CET)
Subject: [XML-SIG] New XML module
In-Reply-To: <1131739549.5807.160.camel@borgia>
References: <ca471dc20511101953ve850477uc73b57a2f25c4a48@mail.gmail.com>
	<1131739549.5807.160.camel@borgia>
Message-ID: <1152.213.6.240.122.1131959812.squirrel@isar.livinglogic.de>

Uche Ogbuji sagte:

> On Thu, 2005-11-10 at 19:53 -0800, Guido van Rossum wrote:
>> At Elemental I've had a lot of success with a simple module that converts between Python data structures and XML. I
>> mentioned this code in a talk at EuroPython this summer and there was quite a bit of interest in it (despite my emphasis on
>> its limitations).
>> [...]
>
> Feels a bit like XIST.

It does indeed.

> Is the class def per element type mandatory?  If not, what do defaults look like?
>
> For my part, I think that there are so many XML processing idioms based on user preference that I'd balk at blessing any one.
>  In retrospect I think it was a mistake to even bless SAX and DOM by putting them in the stdlib.  I think that XML processing
> is parallel to Web frameworks in this respect.  I suppose an equivalent of BaseHTTPServer makes sense, but IMO minidom, SAX
> and pulldom already serve for that.

But BaseHTTPServer doesn't solve the Web framework mess, WSGI might.

So I wonder what a WSGI for XML processing tools might be. Maybe some kind of very minimal Pythonic tree API (i.e. a kind of
Pythonic DOM)? This API should be simple enough, so that ElementTree, lxml, XIST, Guido's tool etc. etc. can implement it
easily. Then we would need only one XPath implementation, only one Relax NG validation implementation etc.
> [...]

Bye,
   Walter D?rwald




From mike at skew.org  Tue Nov 15 05:08:18 2005
From: mike at skew.org (Mike Brown)
Date: Mon, 14 Nov 2005 21:08:18 -0700 (MST)
Subject: [XML-SIG] PyXML vs. stdlib xml.sax - SAX implementation/comparison
	matrix
In-Reply-To: <200510281127.j9SBRbvl014770@chilled.skew.org>
Message-ID: <200511150408.jAF48I8Z065333@chilled.skew.org>

I have a documentation project for someone.

Inspired by the DOM standards compliance matrix[1] and the nonexistence of 
documentation comparing PyXML to stdlib xml.sax, I've created (by hand, by 
looking at source code and CVS logs) an XML document that can be used to 
generate a matrix showing the level of SAX 2.0 and 1.0 support in Python 
stdlib and PyXML: http://skew.org/tmp/sax-in-python.xml

If someone with a few hours to kill would be willing to generate some XSLT to 
render it, that would be great. Perhaps it could also be used to establish 
__all__ in each module, and spot some implementation gaps.

Here is an idea for how the matrix could look when rendered as HTML:
http://skew.org/tmp/sax-in-python.html (just a rough start, actually;
maybe you can think of something better).

The XML should be pretty easy to follow. I intentionally left out a few things 
like ExpatLocator and the driver module contents; they didn't seem to be 
things that would be in the user-level public APIs.

Thanks,
Mike

[1] http://pyxml.sourceforge.net/topics/compliance.html

From list1 at tompassin.net  Wed Nov 16 05:19:43 2005
From: list1 at tompassin.net (Thomas Passin)
Date: Tue, 15 Nov 2005 23:19:43 -0500
Subject: [XML-SIG] PyXML vs. stdlib xml.sax - SAX
 implementation/comparison matrix
In-Reply-To: <200511150408.jAF48I8Z065333@chilled.skew.org>
References: <200511150408.jAF48I8Z065333@chilled.skew.org>
Message-ID: <437AB35F.5020207@tompassin.net>

Mike Brown wrote:
> I have a documentation project for someone.
> 
> Inspired by the DOM standards compliance matrix[1] and the nonexistence of 
> documentation comparing PyXML to stdlib xml.sax, I've created (by hand, by 
> looking at source code and CVS logs) an XML document that can be used to 
> generate a matrix showing the level of SAX 2.0 and 1.0 support in Python 
> stdlib and PyXML: http://skew.org/tmp/sax-in-python.xml
> 
> If someone with a few hours to kill would be willing to generate some XSLT to 
> render it, that would be great. Perhaps it could also be used to establish 
> __all__ in each module, and spot some implementation gaps.

I could take that on, if no one is already doing it.

TomP

From noreply at sourceforge.net  Wed Nov 16 17:44:21 2005
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 16 Nov 2005 08:44:21 -0800
Subject: [XML-SIG] [ pyxml-Patches-1358233 ] pyexpat.py should call
	PyGIL_Acquire
Message-ID: <E1EcQOT-0004Xl-NN@sc8-sf-web2.sourceforge.net>

Patches item #1358233, was opened at 2005-11-16 17:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=306473&aid=1358233&group_id=6473

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: expat
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Raphael Slinckx (kikidonk)
Assigned to: Nobody/Anonymous (nobody)
Summary: pyexpat.py should call PyGIL_Acquire

Initial Comment:
When doing callback into python code from the C code in
pyexpat.c, the GIL should be acquired to avoid
concurrent modifications in the python interpreter.
This problem apears with gtk and gnomevfs, which is
threaded. Sometimes when arsing wml from the thread it
crashes the application.

The patch adds GIL acquire/free when calling back in
python code from pyexpat.c

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=306473&aid=1358233&group_id=6473

From fredrik at pythonware.com  Thu Nov 17 20:06:15 2005
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Thu, 17 Nov 2005 20:06:15 +0100
Subject: [XML-SIG] PyXML vs. stdlib xml.sax - SAX
	implementation/comparisonmatrix
References: <200510281127.j9SBRbvl014770@chilled.skew.org>
	<200511150408.jAF48I8Z065333@chilled.skew.org>
Message-ID: <dlikb3$9mc$1@sea.gmane.org>

Mike Brown wrote:

> If someone with a few hours to kill would be willing to generate some XSLT to
> render it, that would be great.

how about 20 minutes and Python ?

import elementtree.ElementTree as ET

doc = ET.parse("sax-in-python.xml")

class NS:
    def __init__(self, uri):
        self.uri = uri
    def __getattr__(self, tag):
        return self.uri + tag
    def __call__(self, path):
        return "/".join(getattr(self, tag) for tag in path.split("/"))

ns = NS("{http://pyxml.sourceforge.net/SAX-support-matrix/2005/11}")

# get implementation map
implementations = {}
for family in doc.findall(ns("implementations/package-family")):
    for set in family.findall(ns("package-set")):
        for item in set:
            implementations[item.text] = family.get("name"), set.get("name")

def line(indent, *args):
    print "<tr>",
    if len(args) == 1:
        print "<td colspan=3>",
    else:
        print "<td>",
    print "&nbsp;&nbsp;"*indent, "</td><td>".join(args), "</td>",
    print "</tr>"

print """\
<html>
  <head>
    <title>SAX support in Python</title>
    <style type="text/css">
      th { text-align: left }
      th, td { background-color: #EEE; color: 000; }
      body { font-family: sans-serif }
    </style>
  </head>
  <body lang="en">
  <h2>SAX support in Python</h2>
"""

# process technology grid
print "<table>"
for technology in doc.findall(ns.technology):
    line(0, technology.get("name").capitalize())
    thisgroup = None
    for group in technology:
        if group.tag != thisgroup:
            line(1, group.tag.split("}")[1].capitalize())
            thisgroup = group.tag
        line(2, group.get("type").capitalize())
        for item in group:
            name = item.get("name")
            implementation = item.findtext(ns.implementation)
            lib = implementations.get(implementation, ("", ""))
            line(3, name, lib[0], implementation)
print "</table>"

print """\
  </body>
</html>
"""

tweak as necessary.

</F> 




From tjue1 at sussex.ac.uk  Fri Nov 18 17:39:06 2005
From: tjue1 at sussex.ac.uk (Matthew Fowler)
Date: Fri, 18 Nov 2005 16:39:06 +0000
Subject: [XML-SIG] Possible to cross compile?
Message-ID: <1132331946.437e03aa65d81@webmail.sussex.ac.uk>

Hello

Is it possible to cross compile PyXML? Was a little suprised not to see
a configure script. How would one start to go about cross compiling this?

Cheers

Matthew

From jlc6 at po.cwru.edu  Sat Nov 19 22:00:59 2005
From: jlc6 at po.cwru.edu (John L. Clark)
Date: Sat, 19 Nov 2005 13:00:59 -0800
Subject: [XML-SIG] Moving XBEL to SourceForge
Message-ID: <20051119210059.GY1857@rejoice>

Uche Ogbuji proposed that development of XBEL move to an independent
SourceForge project earlier this year[0].  There wasn't a lot of motion
surrounding that idea.  I'd like to renew this interest in breaking XBEL
off into a separately-maintained project.

I have a few questions.  First of all, the points Uche made are still
valid; does this community think that working on XBEL independently is a
good idea, and not too disruptive?  Second, where can we obtain the
currently available XBEL resources (web pages, etc.)?  Finally, who is
still interested in participating, and in what capacity?

I think that if we don't hear a strong negative reaction to this idea
soon, we should go ahead and rev up with this on SourceForge.  I look
forward to hearing your ideas about this and XBEL in general.

Take care,

    John L. Clark

[0] http://mail.python.org/pipermail/xml-sig/2005-February/010901.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.python.org/pipermail/xml-sig/attachments/20051119/ec7663cc/attachment.pgp

From jkmacman at yahoo.com  Mon Nov 21 03:07:37 2005
From: jkmacman at yahoo.com (Jim Kelly)
Date: Sun, 20 Nov 2005 18:07:37 -0800 (PST)
Subject: [XML-SIG] XML-SIG Digest, Vol 31, Issue 13
In-Reply-To: <mailman.5.1132484402.3761.xml-sig@python.org>
Message-ID: <20051121020737.5839.qmail@web50008.mail.yahoo.com>

Does this group cover xbrl or onix at all?
   
   
  kind regards
   
  jjk
  

xml-sig-request at python.org wrote:
  Send XML-SIG mailing list submissions to
xml-sig at python.org

To subscribe or unsubscribe via the World Wide Web, visit
http://mail.python.org/mailman/listinfo/xml-sig
or, via email, send a message with subject or body 'help' to
xml-sig-request at python.org

You can reach the person managing the list at
xml-sig-owner at python.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of XML-SIG digest..."


Today's Topics:

1. Moving XBEL to SourceForge (John L. Clark)


----------------------------------------------------------------------

Message: 1
Date: Sat, 19 Nov 2005 13:00:59 -0800
From: "John L. Clark" 
Subject: [XML-SIG] Moving XBEL to SourceForge
To: xml-sig at python.org
Message-ID: <20051119210059.GY1857 at rejoice>
Content-Type: text/plain; charset="us-ascii"

Uche Ogbuji proposed that development of XBEL move to an independent
SourceForge project earlier this year[0]. There wasn't a lot of motion
surrounding that idea. I'd like to renew this interest in breaking XBEL
off into a separately-maintained project.

I have a few questions. First of all, the points Uche made are still
valid; does this community think that working on XBEL independently is a
good idea, and not too disruptive? Second, where can we obtain the
currently available XBEL resources (web pages, etc.)? Finally, who is
still interested in participating, and in what capacity?

I think that if we don't hear a strong negative reaction to this idea
soon, we should go ahead and rev up with this on SourceForge. I look
forward to hearing your ideas about this and XBEL in general.

Take care,

John L. Clark

[0] http://mail.python.org/pipermail/xml-sig/2005-February/010901.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.python.org/pipermail/xml-sig/attachments/20051119/ec7663cc/attachment-0001.pgp

End of XML-SIG Digest, Vol 31, Issue 13
***************************************
  


		
---------------------------------
 Yahoo! FareChase - Search multiple travel sites in one click.  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/xml-sig/attachments/20051120/7945a10a/attachment.html

From Bernard.Venemans at tass-safe.com  Tue Nov 22 14:53:28 2005
From: Bernard.Venemans at tass-safe.com (Venemans, Bernard)
Date: Tue, 22 Nov 2005 14:53:28 +0100
Subject: [XML-SIG] Sax2 import
Message-ID: <4F2F2E8B0EE58145A9D6FF8A05CC891E17AAD5@sw009.wdm.local>

I installed Python 2.4 and PyXML 0.8.3 in order to be able to run a
script that converts an XML log to HTML (see attachment). On Windows
this works fine, but I cannot get it to work on Solaris 9.
 
I get the following output... 
 
~/squish-2.0.1/projects> /usr/local/bin/python
./lib/GenerateHtmlReport.py
/usr/local
['/mnt/usr3/people/venemab/squish-2.0.1/projects/lib',
'/usr/local/lib/python24.zip', '/usr/local/lib/python2.4',
'/usr/local/lib/python2.4/plat-sunos5',
'/usr/local/lib/python2.4/lib-tk',
'/usr/local/lib/python2.4/lib-dynload',
'/usr/local/lib/python2.4/site-packages']
Traceback (most recent call last):
  File "./lib/GenerateHtmlReport.py", line 11, in ?
    from xml.dom.ext.reader import Sax2
ImportError: No module named ext.reader

...when I execute the following piece of code (see attachment for
complete python file):
 
#!/usr/bin/env python
# -*- coding: Latin-1 -*-
 
import sys
print sys.prefix
print sys.path
 
from xml.dom.NodeFilter import NodeFilter
from xml.dom import Node
# 
http://sourceforge.net/project/showfiles.php?group_id=6473&package_id=65
41&release_id=174846
from xml.dom.ext.reader import Sax2
 
 
I installed PyXML with 'python setup.py install' which resulted in an
_xmlplus directory structure being added to
/usr/local/lib/python2.4/site-packages.
Anybody any idea what goes wrong here?
 
Thanks, Bernard Venemans

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/xml-sig/attachments/20051122/18349f26/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GenerateHtmlReport.py
Type: application/octet-stream
Size: 4024 bytes
Desc: GenerateHtmlReport.py
Url : http://mail.python.org/pipermail/xml-sig/attachments/20051122/18349f26/GenerateHtmlReport.obj

From Uche.Ogbuji at fourthought.com  Wed Nov 23 22:03:16 2005
From: Uche.Ogbuji at fourthought.com (Uche Ogbuji)
Date: Wed, 23 Nov 2005 14:03:16 -0700
Subject: [XML-SIG] Moving XBEL to SourceForge
In-Reply-To: <20051119210059.GY1857@rejoice>
References: <20051119210059.GY1857@rejoice>
Message-ID: <1132779796.842.82.camel@borgia>

On Sat, 2005-11-19 at 13:00 -0800, John L. Clark wrote:
> Uche Ogbuji proposed that development of XBEL move to an independent
> SourceForge project earlier this year[0].  There wasn't a lot of motion
> surrounding that idea.  I'd like to renew this interest in breaking XBEL
> off into a separately-maintained project.
> 
> I have a few questions.  First of all, the points Uche made are still
> valid; does this community think that working on XBEL independently is a
> good idea, and not too disruptive?  Second, where can we obtain the
> currently available XBEL resources (web pages, etc.)?  Finally, who is
> still interested in participating, and in what capacity?
> 
> I think that if we don't hear a strong negative reaction to this idea
> soon, we should go ahead and rev up with this on SourceForge.  I look
> forward to hearing your ideas about this and XBEL in general.

I'd say that considering there were not objections last time it came up,
and we've had a few days again for people to ponder objections, it's
time to just go ahead and do it.  Thanks for offering to help do so.


-- 
Uche Ogbuji                               Fourthought, Inc.
http://uche.ogbuji.net                    http://fourthought.com
http://copia.ogbuji.net                   http://4Suite.org
Articles: http://uche.ogbuji.net/tech/publications/


From jlc6 at po.cwru.edu  Thu Nov 24 00:35:24 2005
From: jlc6 at po.cwru.edu (John L. Clark)
Date: Wed, 23 Nov 2005 15:35:24 -0800
Subject: [XML-SIG] Moving XBEL to SourceForge
In-Reply-To: <1132779796.842.82.camel@borgia>
References: <20051119210059.GY1857@rejoice> <1132779796.842.82.camel@borgia>
Message-ID: <20051123233524.GG1857@rejoice>

On Wed, Nov 23, 2005 at 02:03:16PM -0700, Uche Ogbuji wrote:
> > I think that if we don't hear a strong negative reaction to this idea
> > soon, we should go ahead and rev up with this on SourceForge.

> I'd say that considering there were not objections last time it came up,
> and we've had a few days again for people to ponder objections, it's
> time to just go ahead and do it.  Thanks for offering to help do so.

Alright, I've submitted the registration for a project creatively named
`xbel` on SourceForge.  In my little dream world one of the SourceForge
Gurus will just happen to notice it in her inbox immediately, look at
it, and say "Oh, that's a no-brainer" and press the little green button
(or whatever color it might be) so that I can get started ASAP getting
stuff set up.  Buuuut, given what week it is, and the fact that they say
two days, I'm guessing sometime next week we may see some movement.

And, speaking of the week... I'm definitely thankful for this little
bookmark language, and for all of the hard work by the community on the
supporting standards (XML, URI, etc.), and I'm thankful to so many for
so much more.  Happy Thanksgiving to all of you.

Take care,

    John L. Clark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.python.org/pipermail/xml-sig/attachments/20051123/c869d89b/attachment.pgp

From noreply at sourceforge.net  Thu Nov 24 15:43:12 2005
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 24 Nov 2005 06:43:12 -0800
Subject: [XML-SIG] [ pyxml-Bugs-1365605 ] PrettyPrint with UTF-16 encoding
	produces invalid XML.
Message-ID: <E1EfIJc-0007kR-93@sc8-sf-web3.sourceforge.net>

Bugs item #1365605, was opened at 2005-11-24 14:43
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=1365605&group_id=6473

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: MikeW (mrdubya)
Assigned to: Nobody/Anonymous (nobody)
Summary: PrettyPrint with UTF-16 encoding produces invalid XML.

Initial Comment:
Every string written to the output stream by
PrettyPrint() has the default BOM prefixed to it. 
Using the UTF-16LE encoding stops any BOM from
appearing in the output stream, including before the
XML declaration.  This means that the resultant XML is
not valid (section 4.3.3 XML 1.0 3e).

Element attribute output is also invalid.  The =" and
final " are not encoded so end up pairing up with bytes
from the BOM codepoint.  Using UTF-16LE does not
correct the output for similar reasons.

I assume UTF-32 output will suffer from the similar
problems.

PyXML version 0.8.4 and Python version 2.4.1

Example code:

dom = Document.Document(None)
element = dom.createElement('HelloWorld')
element.setAttribute('Language', 'English')
dom.appendChild(element)
PrettyPrint(dom, stream=file('./pp.xml', 'w+b'),
encoding='UTF-16')


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106473&aid=1365605&group_id=6473

From noreply at sourceforge.net  Thu Nov 24 23:32:04 2005
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 24 Nov 2005 14:32:04 -0800
Subject: [XML-SIG] [ pyxml-Patches-1365920 ] Support UTF-16 encoding when
	PrettyPrinting.
Message-ID: <E1EfPdM-0005Kt-SU@sc8-sf-web2.sourceforge.net>

Patches item #1365920, was opened at 2005-11-24 22:32
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=306473&aid=1365920&group_id=6473

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: MikeW (mrdubya)
Assigned to: Nobody/Anonymous (nobody)
Summary: Support UTF-16 encoding when PrettyPrinting.

Initial Comment:
Patch for request id 1365605.

The attached unified diff to _xmlplus/dom/ext modifies
PrettyPrint to generate valid XML for UTF-16, UTF-16LE
and UTF-16BE encodings.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=306473&aid=1365920&group_id=6473

From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:25 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:25 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101525.1830.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<proennekejr at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:25 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:25 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101525.1831.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<jarsofclay413 at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:25 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:25 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101525.1828.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<hannah.brown at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:25 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:25 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101525.1858.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<MSN_Newsletters at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:25 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:25 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101525.1862.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<BrookeMcLaughlin_08 at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:25 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:25 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101525.1863.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<kbock at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:26 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:26 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101526.1919.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<kanderson at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:26 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:26 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101526.1921.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<soundoff at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:26 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:26 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101526.1927.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<lmckay at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:26 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:26 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101526.1973.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<all_students at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:26 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:26 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101526.1930.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<sdowns at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:26 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:26 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101526.1974.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<cfn at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:26 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:26 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101526.1988.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<pete at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:26 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:26 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101526.1994.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<fpams004 at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:26 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:26 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101526.1997.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<lsheehy at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2035.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<scouchman at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:26 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:26 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101526.1993.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<lcox at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:26 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:26 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101526.2007.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<blalock00 at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2036.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<peterbelesis at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2078.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<alogue at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2096.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<rpeterson at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2099.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<customerservice at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2097.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<ndic at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2136.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<macintosh at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2135.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<saleshelp at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2137.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<beihl at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2144.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<privacy at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2157.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<ben at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2190.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<ccarlen at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2191.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<mj at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:27 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:27 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101527.2196.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<law at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2209.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<slamm at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2219.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<samuel at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2239.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<akhil.arora at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2238.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<rjc at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2255.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<christopher at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2271.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<Tomi.Leppikangas at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2288.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<bsmedberg at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2289.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<bnesse at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2290.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<bodahlstrom at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2293.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<mitesh at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2339.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<jef at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2342.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<apache at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2347.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<justin at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2350.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<sax at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:29 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:29 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101529.2378.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<david at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:28 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:28 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101528.2361.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<site-policy at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:29 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:29 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101529.2468.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<bbb at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:29 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:29 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101529.2466.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<hewitt at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:29 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:29 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101529.2467.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<ppp-request at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:29 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:29 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101529.2532.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<gward at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From badaddressbounce at alamobowl.com  Sun Nov 27 11:15:29 2005
From: badaddressbounce at alamobowl.com (badaddressbounce@alamobowl.com)
Date: 27 Nov 2005 04:15:29 -0600
Subject: [XML-SIG] failure notice
Message-ID: <20051127101529.2540.qmail@mailserver.alamobowl.com>

Hi. This is the qmail-send program at alamobowl.com.
I'm afraid I wasn't able to deliver your message to the following
addresses:

<jar at alamobowl.com>
553 5.3.0 User unknown 

This is a permanent error; I've given up. Sorry it didn't work out. Please
don't reply to this message, all replies will automatically be discarded. 
If you have questions, please call the number below.

www.alamobowl.com
(210) 226-2695


From jlc6 at po.cwru.edu  Mon Nov 28 07:04:27 2005
From: jlc6 at po.cwru.edu (John L. Clark)
Date: Sun, 27 Nov 2005 22:04:27 -0800
Subject: [XML-SIG] Moving XBEL to SourceForge
In-Reply-To: <20051123233524.GG1857@rejoice>
References: <20051119210059.GY1857@rejoice> <1132779796.842.82.camel@borgia>
	<20051123233524.GG1857@rejoice>
Message-ID: <20051128060427.GG4653@rejoice>

On Wed, Nov 23, 2005 at 03:35:24PM -0800, John L. Clark wrote:
> On Wed, Nov 23, 2005 at 02:03:16PM -0700, Uche Ogbuji wrote:
> > I'd say that considering there were not objections last time it came up,
> > and we've had a few days again for people to ponder objections, it's
> > time to just go ahead and do it.  Thanks for offering to help do so.
> 
> Alright, I've submitted the registration for a project creatively named
> `xbel` on SourceForge.

The `xbel` project[0] has been activated on SourceForge, and I've
started things out by setting up a mailing list called XBEL-Specs.  You
can read a bit more about that at the first thread of the list[1].  I
would encourage anyone who is interested in the XBEL project to start
throwing ideas around over there.

The list does not require registration to post, so hopefully it will be
convenient to simply shoot messages to the list whenever the need
arises.

Take care,

    John L. Clark

[0] http://sourceforge.net/projects/xbel/

[1] http://sourceforge.net/mailarchive/message.php?msg_id=13995995
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.python.org/pipermail/xml-sig/attachments/20051127/23a2db0f/attachment.pgp

From Meghan.Sullivan at vwcredit.com  Mon Nov 28 18:51:00 2005
From: Meghan.Sullivan at vwcredit.com (Sullivan, Meghan)
Date: Mon, 28 Nov 2005 11:51:00 -0600
Subject: [XML-SIG]  {Virus?} Delivery failed
Message-ID: <C6A3FAE95BB3B3468EA896AF65010C2701088FF3@usvcilvx004.usvci001.vci.na.vwg>

 

 

Meghan E. Sullivan

VW Credit, Inc.

Project Manager - Application Development

(Work) 847-371-4161

(Cell) 847-514-8504

(Fax) 847-281-4368

 



*********************************************************************** 
DISCLAIMER:
The information transmitted may contain confidential material and is
intended only for the person or entity to which it is addressed.  Any
review, retransmission, dissemination or other use of or taking of any
action by persons or entities other than the intended recipient is
prohibited.  If you are not the intended recipient, please delete the
information from your system and contact the sender.
 ***********************************************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/xml-sig/attachments/20051128/e6ab4f65/attachment.htm

From tony.mcdonald at ncl.ac.uk  Tue Nov 29 08:38:58 2005
From: tony.mcdonald at ncl.ac.uk (Tony McDonald)
Date: Tue, 29 Nov 2005 07:38:58 +0000
Subject: [XML-SIG] How do I replace multiple elements in a document? (using
	ElementTree)
Message-ID: <6D5F2A11-8201-4ED2-9208-C22D5D08239C@ncl.ac.uk>

Hi,
I'd like to convert a document (docbook format actually) like this;

<article>
<para>preamble</para>
<para role="book">EMED123</para>
<some
...
<para role="book">RMED789</para>
</article>

(para can be nested)

With something that looks like this
<article>
<para>preamble</para>
<biblioentry>
<title>Human histology</title>
<edition>3rd ed. 2004</edition>
<para >31.99</para>
<author>Stevens,  A &amp; Lowe, J S</author>
...
</biblioentry>

(biblioentry can be repeated). That is, the original <para  
role="book">EMED123</para> should be totally replaced by the  
biblioentry element(s).

The code EMED123 is used as a key into a database to look up the book  
entries. We then generate biblioentry(s) from it. That works fine,  
and I'm creating Elements from that happily.

What I *cannot* get right is the replacement. I've tried append but  
that seems to work so;

xml = """<?xml version="1.0"?>
<doc>
<begin>start</begin>
<replaceme>with something else</replaceme>
<end>finish</end>
</doc>
"""
root = XML(xml)
new = Element("new")
new.text = "Hi"
elements = root.getiterator()
for element in elements:
     if element.tag == 'replaceme':
         element.append(new)
dump(root)

Produces this;
<doc>
<begin>start</begin>
<replaceme arg="EMED">with something else derived from <new>Hi</new></ 
replaceme>
<end>finish</end>
</doc>

Which is not what I expected. I expected this;
<doc>
<begin>start</begin>
<replaceme>with something else</replaceme><new>Hi</new>
<end>finish</end>
</doc>

As a first step to replacing my document, but no joy so far...

Can anyone help out here?

cheers
Tone
-- 
Dr Tony McDonald, Asst Director, FMSC. 0191 246 4543
School of Medical Education Development
Project Manager, FDTL-4 ePortfolios http://www.eportfolios.ac.uk/


From meonimarco at gmail.com  Tue Nov 29 11:47:49 2005
From: meonimarco at gmail.com (Marco Meoni)
Date: Tue, 29 Nov 2005 11:47:49 +0100
Subject: [XML-SIG] Build a dinamic GUI from a DTD file
Message-ID: <438C31D5.9060108@gmail.com>

Hi, i'm new in python programming and i'm new in this mailing list.
I have a problem in buildin a GUI with wxpython. My application have to 
start by GUI. This GUI have to be dinamic. The commands that the GUI 
have to show are described in a DTD. The GUI must read the DTD file and 
show the command that is in DTD file (in every start of the program).
How can I do this?
Is there any simple py files that you can send me for examples in 
managing DTD or XML with Python?
Sorry for my bad english but i'm an italian boy...
Thanks to all!
Marco.
-- 

mail address:

meonimarco at gmail.com <mailto:meonimarco at gmail.com>

web site:

www.marcomeoni.net <http://www.marcomeoni.net>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/xml-sig/attachments/20051129/0bf7afc7/attachment.htm

From fredrik at pythonware.com  Tue Nov 29 12:47:58 2005
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Tue, 29 Nov 2005 12:47:58 +0100
Subject: [XML-SIG] How do I replace multiple elements in a document?
	(using ElementTree)
References: <6D5F2A11-8201-4ED2-9208-C22D5D08239C@ncl.ac.uk>
Message-ID: <dmhf5h$qhi$1@sea.gmane.org>

Tony McDonald wrote:

> (biblioentry can be repeated). That is, the original <para
> role="book">EMED123</para> should be totally replaced by the
> biblioentry element(s).
>
> The code EMED123 is used as a key into a database to look up the book
> entries. We then generate biblioentry(s) from it. That works fine,
> and I'm creating Elements from that happily.
>
> What I *cannot* get right is the replacement. I've tried append but
> that seems to work so;
>
> xml = """<?xml version="1.0"?>
> <doc>
> <begin>start</begin>
> <replaceme>with something else</replaceme>
> <end>finish</end>
> </doc>
> """
> root = XML(xml)
> new = Element("new")
> new.text = "Hi"
> elements = root.getiterator()
> for element in elements:
>      if element.tag == 'replaceme':
>          element.append(new)
> dump(root)
>
> Produces this;
> <doc>
> <begin>start</begin>
> <replaceme arg="EMED">with something else derived from <new>Hi</new></
> replaceme>
> <end>finish</end>
> </doc>

how about:

xml = """<?xml version="1.0"?>
<doc>
<begin>start</begin>
<replaceme>with something else</replaceme>
<end>finish</end>
</doc>
"""

root = XML(xml)

new = Element("new")
new.text = "Hi"
new.tail = "\n"

for index, element in enumerate(root):
     if element.tag == 'replaceme':
         root[index] = new
dump(root)

this prints

<doc>
<begin>start</begin>
<new>Hi</new>
<end>finish</end>
</doc>

to do this recursively, you can either put the code in a function
that calls itself, or you can simply add an extra loop:

for parent in root.getiterator():
    for index, element in enumerate(parent):
        if element.tag == 'replaceme':
            parent[index] = new

hope this helps!

</F>




From tony.mcdonald at ncl.ac.uk  Wed Nov 30 13:50:13 2005
From: tony.mcdonald at ncl.ac.uk (Tony McDonald)
Date: Wed, 30 Nov 2005 12:50:13 +0000
Subject: [XML-SIG] How do I replace multiple elements in a document?
	(using ElementTree)
In-Reply-To: <dmhf5h$qhi$1@sea.gmane.org>
References: <6D5F2A11-8201-4ED2-9208-C22D5D08239C@ncl.ac.uk>
	<dmhf5h$qhi$1@sea.gmane.org>
Message-ID: <436A9F11-3108-4464-AFCB-E5EC12957258@ncl.ac.uk>


On 29 Nov 2005, at 11:47, Fredrik Lundh wrote:

Apologies for replying a bit late, I was trying to fix things up  
myself and didn't check back with the mailing list until later...

>
> how about:
>
> xml = """<?xml version="1.0"?>
> <doc>
> <begin>start</begin>
> <replaceme>with something else</replaceme>
> <end>finish</end>
> </doc>
> """
>
> root = XML(xml)
>
> new = Element("new")
> new.text = "Hi"
> new.tail = "\n"
>
> for index, element in enumerate(root):
>      if element.tag == 'replaceme':
>          root[index] = new
> dump(root)
>
> this prints
>
> <doc>
> <begin>start</begin>
> <new>Hi</new>
> <end>finish</end>
> </doc>
>

* -- blinks -- *

enumerate? you can tell who's not been keeping up with python release  
notes...

I had been using the findIndex function that Greg Wilson posted a  
while back (thanks Greg!)

     def findIndex(parent, child):
         for i in range(len(parent)):
             if parent[i] is child:
                 return i
         return -1

But this is more *elegant*

> to do this recursively, you can either put the code in a function
> that calls itself, or you can simply add an extra loop:
>
> for parent in root.getiterator():
>     for index, element in enumerate(parent):
>         if element.tag == 'replaceme':
>             parent[index] = new
>
> hope this helps!
>

Oh it does, it does - many thanks indeed!

BTW (everyone), what's the correct import procedure to get  
cElementTree goodness?

I did have this,

from elementtree.ElementTree import XML, ElementTree, Element,  
SubElement, dump

and went to this;

from cElementTree import XML, ElementTree, Element, SubElement, dump

Which imports fine, but there's something amiss because;
root = ElementTree(file=filename)
...
elements = root.getiterator()
print "LEN", len(elements)

which gave 634 elements using python ElementTree but gives len() of  
unsized object when using the eElementTree version, and there does  
seem to be something amiss ...

python 2.4.1, OS-X 10.4.3

dir(elements) - cElementTree (version 1.0.2)
['__class__', '__delattr__', '__doc__', '__getattribute__',  
'__hash__', '__init__', '__iter__', '__new__', '__reduce__',  
'__reduce_ex__', '__repr__', '__setattr__', '__str__', 'gi_frame',  
'gi_running', 'next']

dir(elements) - python ElementTree (version 1.2)
['__add__', '__class__', '__contains__', '__delattr__',  
'__delitem__', '__delslice__', '__doc__', '__eq__', '__ge__',  
'__getattribute__', '__getitem__', '__getslice__', '__gt__',  
'__hash__', '__iadd__', '__imul__', '__init__', '__iter__', '__le__',  
'__len__', '__lt__', '__mul__', '__ne__', '__new__', '__reduce__',  
'__reduce_ex__', '__repr__', '__reversed__', '__rmul__',  
'__setattr__', '__setitem__', '__setslice__', '__str__', 'append',  
'count', 'extend', 'index', 'insert', 'pop', 'remove', 'reverse',  
'sort']

Which is 'beyond my ken...'

I can stick with python ElementTree if needed, but many thanks for  
any pointers!

cheers,
Tone
-- 
Dr Tony McDonald, Asst Director, FMSC. 0191 246 4543
School of Medical Education Development
Project Manager, FDTL-4 ePortfolios http://www.eportfolios.ac.uk/


From fredrik at pythonware.com  Wed Nov 30 17:27:38 2005
From: fredrik at pythonware.com (Fredrik Lundh)
Date: Wed, 30 Nov 2005 17:27:38 +0100
Subject: [XML-SIG] How do I replace multiple elements in a
	document?(using ElementTree)
References: <6D5F2A11-8201-4ED2-9208-C22D5D08239C@ncl.ac.uk><dmhf5h$qhi$1@sea.gmane.org>
	<436A9F11-3108-4464-AFCB-E5EC12957258@ncl.ac.uk>
Message-ID: <dmkjtu$l97$1@sea.gmane.org>

Tony McDonald wrote:

> I did have this,
>
> from elementtree.ElementTree import XML, ElementTree, Element,
> SubElement, dump
>
> and went to this;
>
> from cElementTree import XML, ElementTree, Element, SubElement, dump
>
> Which imports fine, but there's something amiss because;
> root = ElementTree(file=filename)
> ...
> elements = root.getiterator()
> print "LEN", len(elements)
>
> which gave 634 elements using python ElementTree but gives len() of
> unsized object when using the eElementTree version, and there does
> seem to be something amiss ...

the getiterator method is defined to return "something that you can
iterate over", which is not necessarily a sequence object.

in ElementTree, it happens to be a list (at least in the 1.2 series), but
cElementTree returns a generator instead.

no matter what version you're using, this

    for elem in root.getiterator():
        ...

is guaranteed to work.  if you want a list, you can always use the list
constructor. e.g.

    print "LEN", len(list(root.getiterator()))

</F>