From ken.beesley at xrce.xerox.com Thu Sep 1 11:47:04 2005 From: ken.beesley at xrce.xerox.com (Ken Beesley) Date: Thu, 01 Sep 2005 11:47:04 +0200 Subject: [XML-SIG] Corrected list of packages handling XML 1.1 In-Reply-To: References: Message-ID: <4316CE18.6070102@xrce.xerox.com> My apologies to Fredrik Lundh of Pythonware for the omission of ElementType+sgmlop in my recent listing of Python-XML packages that handle XML 1.1. The list (that I'm aware of) currently includes: 1. pxdom by Andrew Clover (http://www.doxdesk.com/software/py/pxdom.html, http://www.doxdesk.com/file/software/py/pxdom.py) 2. pyLTXML from the Univ. of Edinburgh (http://www.ltg.ed.ac.uk/software/xml, http://www.ltg.ed.ac.uk/software/gpl_xml.html, http://www.ltg.ed.ac.uk/software/xml/xmldoc/xmldoc.html) 3. elementtree library from Pythonware (http://effbot.org/zone/element.htm, http://effbot.org/zone/element-index.htm) If I've forgotten anyone, please help me complete the list. I'm still a Python-XML beginner, and any omissions are unintentional. Thanks again to all those who have provided such tools. Ken Fredrik Lundh wrote fwiw, as the following snippet illustrates, ET+sgmlop can read files with 1.1-style character references, but the ET serializer doesn't encode such characters on the way out. this script from elementtree import ElementTree, SgmlopXMLTreeBuilder from StringIO import StringIO file = StringIO("this is a backspace: ") doc = ElementTree.parse(file, SgmlopXMLTreeBuilder.TreeBuilder()) root = doc.getroot() print repr(root.text) print repr(ElementTree.tostring(root)) prints 'this is a backspace: \x08' 'this is a backspace: \x08' which isn't entirely correct. fixing this in ElementTree is pretty straightforward; just tweak the RE, and make sure _encode_entity is called for all cdata sections. you can also use the following brute-force runtime patch: # patch the ET serializer (works with 1.2.X, may break beyond that) import re from elementtree import ElementTree escape = re.compile(u'[&<>\"\x01-\x09\x0b\x0c\x0e-\x1f\u0080-\uffff]+') ElementTree._encode_entity.func_defaults = (escape,) ElementTree._escape_cdata = lambda a, b: ElementTree._encode_entity(a) # end From walter at livinglogic.de Thu Sep 1 12:50:08 2005 From: walter at livinglogic.de (=?ISO-8859-1?Q?Walter_D=F6rwald?=) Date: Thu, 01 Sep 2005 12:50:08 +0200 Subject: [XML-SIG] Corrected list of packages handling XML 1.1 In-Reply-To: <4316CE18.6070102@xrce.xerox.com> References: <4316CE18.6070102@xrce.xerox.com> Message-ID: <4316DCE0.1080902@livinglogic.de> Ken Beesley wrote: > My apologies to Fredrik Lundh of Pythonware for the omission of > ElementType+sgmlop in my recent listing of Python-XML packages that > handle XML 1.1. The list (that I'm aware of) currently includes: 1. > pxdom by Andrew Clover (http://www.doxdesk.com/software/py/pxdom.html, > http://www.doxdesk.com/file/software/py/pxdom.py) 2. pyLTXML from the > Univ. of Edinburgh (http://www.ltg.ed.ac.uk/software/xml, > http://www.ltg.ed.ac.uk/software/gpl_xml.html, > http://www.ltg.ed.ac.uk/software/xml/xmldoc/xmldoc.html) 3. elementtree > library from Pythonware (http://effbot.org/zone/element.htm, > http://effbot.org/zone/element-index.htm) If I've forgotten anyone, > please help me complete the list. > [...] XIST (http://www.livinglogic.de/Python/xist) handles XML 1.1 charrefs when a parser is used that does it. (XIST uses sgmlop by default, so it works by default). When serializing XML those charrefs are always supported. See the following snippet: >>> from ll.xist import parsers, presenters >>> from ll.xist.ns import html >>> e = parsers.parseString("this is a backspace: ") >>> print e.asrepr(presenters.CodePresenter()) ll.xist.xsc.Frag( ll.xist.ns.html.body( 'this is a backspace: \x08' ) ) >>> print e.asBytes() this is a backspace: Bye, Walter D?rwald From Uche.Ogbuji at fourthought.com Thu Sep 1 19:59:09 2005 From: Uche.Ogbuji at fourthought.com (Uche Ogbuji) Date: Thu, 01 Sep 2005 11:59:09 -0600 Subject: [XML-SIG] Corrected list of packages handling XML 1.1 In-Reply-To: <4316DCE0.1080902@livinglogic.de> References: <4316CE18.6070102@xrce.xerox.com> <4316DCE0.1080902@livinglogic.de> Message-ID: <1125597549.14255.347.camel@borgia> On Thu, 2005-09-01 at 12:50 +0200, Walter D?rwald wrote: > Ken Beesley wrote: > > > My apologies to Fredrik Lundh of Pythonware for the omission of > > ElementType+sgmlop in my recent listing of Python-XML packages that > > handle XML 1.1. The list (that I'm aware of) currently includes: 1. > > pxdom by Andrew Clover (http://www.doxdesk.com/software/py/pxdom.html, > > http://www.doxdesk.com/file/software/py/pxdom.py) 2. pyLTXML from the > > Univ. of Edinburgh (http://www.ltg.ed.ac.uk/software/xml, > > http://www.ltg.ed.ac.uk/software/gpl_xml.html, > > http://www.ltg.ed.ac.uk/software/xml/xmldoc/xmldoc.html) 3. elementtree > > library from Pythonware (http://effbot.org/zone/element.htm, > > http://effbot.org/zone/element-index.htm) If I've forgotten anyone, > > please help me complete the list. > > [...] > > XIST (http://www.livinglogic.de/Python/xist) handles XML 1.1 charrefs > when a parser is used that does it. (XIST uses sgmlop by default, so it > works by default). When serializing XML those charrefs are always > supported. See the following snippet: > > >>> from ll.xist import parsers, presenters > >>> from ll.xist.ns import html > >>> e = parsers.parseString("this is a backspace: ") > >>> print e.asrepr(presenters.CodePresenter()) > ll.xist.xsc.Frag( > ll.xist.ns.html.body( > 'this is a backspace: \x08' > ) > ) > >>> print e.asBytes() > this is a backspace: This conversation is really becoming surreal. People, please, it's very simple: supporting the range of character references defined in XML 1.1. Is not, repeat *NOT* the same thing as being an XML 1.1 parser. If I have software that parses "b" that does not mean I have an XML 1.0 parser. If that software also accepts "b", then it is obviously not such. Any software that accepts "this is a backspace: " is neither a compliant XML 1.0 parser nor a compliant XML 1.1. parser. All XML 1.1 documents *must have an XML declaration* according to the strict stipulation of the spec. If an XML 1.1. parser encounters a document without an XML declaration, it *must* assume that it is an XML 1.0 document, at which point it would *have to* stop with a fatal error when it encounters . Period. There is no negotiation here. Therefore, as far as I can tell, neither the ET/sgmlop trick nor XIST are XML 1.1. parsers. I cannot speak for LTXML or pxdom, but knowing the authors, I would guess that they are indeed compliant XML 1.1 parsers. -- Uche Ogbuji Fourthought, Inc. http://uche.ogbuji.net http://fourthought.com http://copia.ogbuji.net http://4Suite.org Use CSS to display XML, part 2 - http://www-128.ibm.com/developerworks/edu/x-dw-x-xmlcss2-i.html XML Output with 4Suite & Amara - http://www.xml.com/pub/a/2005/04/20/py-xml.html Use XSLT to prepare XML for import into OpenOffice Calc - http://www.ibm.com/developerworks/xml/library/x-oocalc/ Schema standardization for top-down semantic transparency - http://www-128.ibm.com/developerworks/xml/library/x-think31.html From ken.beesley at xrce.xerox.com Fri Sep 2 17:54:56 2005 From: ken.beesley at xrce.xerox.com (Ken Beesley) Date: Fri, 02 Sep 2005 17:54:56 +0200 Subject: [XML-SIG] Corrected list of packages handling XML 1.1 In-Reply-To: References: Message-ID: <431875D0.6050304@xrce.xerox.com> Uche Ogbuji wrote >------------------------------ > >Message: 2 >Date: Thu, 01 Sep 2005 11:59:09 -0600 >From: Uche Ogbuji >Subject: Re: [XML-SIG] Corrected list of packages handling XML 1.1 >To: Walter D?rwald >Cc: xml-sig at python.org, Ken Beesley >Message-ID: <1125597549.14255.347.camel at borgia> >Content-Type: text/plain; charset=ISO-8859-15 > >On Thu, 2005-09-01 at 12:50 +0200, Walter D?rwald wrote: > > >>Ken Beesley wrote: >> >> >> >>>My apologies to Fredrik Lundh of Pythonware for the omission of >>>ElementType+sgmlop in my recent listing of Python-XML packages that >>>handle XML 1.1. The list (that I'm aware of) currently includes: 1. >>>pxdom by Andrew Clover (http://www.doxdesk.com/software/py/pxdom.html, >>>http://www.doxdesk.com/file/software/py/pxdom.py) 2. pyLTXML from the >>>Univ. of Edinburgh (http://www.ltg.ed.ac.uk/software/xml, >>>http://www.ltg.ed.ac.uk/software/gpl_xml.html, >>>http://www.ltg.ed.ac.uk/software/xml/xmldoc/xmldoc.html) 3. elementtree >>>library from Pythonware (http://effbot.org/zone/element.htm, >>>http://effbot.org/zone/element-index.htm) If I've forgotten anyone, >>>please help me complete the list. >>> >>> >> > [...] >> >>XIST (http://www.livinglogic.de/Python/xist) handles XML 1.1 charrefs >>when a parser is used that does it. (XIST uses sgmlop by default, so it >>works by default). When serializing XML those charrefs are always >>supported. See the following snippet: >> >> >>> from ll.xist import parsers, presenters >> >>> from ll.xist.ns import html >> >>> e = parsers.parseString("this is a backspace: ") >> >>> print e.asrepr(presenters.CodePresenter()) >>ll.xist.xsc.Frag( >> ll.xist.ns.html.body( >> 'this is a backspace: \x08' >> ) >>) >> >>> print e.asBytes() >>this is a backspace: >> >> > >This conversation is really becoming surreal. People, please, it's very >simple: supporting the range of character references defined in XML 1.1. >Is not, repeat *NOT* the same thing as being an XML 1.1 parser. > >If I have software that parses "b" that does not mean I have an >XML 1.0 parser. If that software also accepts "b", then it is >obviously not such. > >Any software that accepts "this is a backspace: " >is neither a compliant XML 1.0 parser nor a compliant XML 1.1. parser. >All XML 1.1 documents *must have an XML declaration* according to the >strict stipulation of the spec. If an XML 1.1. parser encounters a >document without an XML declaration, it *must* assume that it is an XML >1.0 document, at which point it would *have to* stop with a fatal error >when it encounters . Period. There is no negotiation here. > >Therefore, as far as I can tell, neither the ET/sgmlop trick nor XIST >are XML 1.1. parsers. I cannot speak for LTXML or pxdom, but knowing >the authors, I would guess that they are indeed compliant XML 1.1 >parsers. > > > > What Mr. Ogbuji states about "being an XML 1.1 parser" and "being a compliant XML 1.0 parser [or] a compliant XML 1.1 parser" is of course correct. However, with respect, I believe that he misses the point and claims of the list. I posted a list of packages "handling XML 1.1", and Martin D?rwald helpfully added XIST as a package that "handles XML 1.1 charrefs when a parser [like sgmlop] is used that does it". Neither one of us claimed that all the listed packages (and especially not the ones using an underlying sgmlop parser) were "XML 1.1 parsers". Perhaps my terminology is confusing, but what I meant by "handling XML 1.1" is this: "Handle XML 1.1" = able to process a valid XML 1.1 document without throwing up and quitting. Sgmlop (http://effbot.org/zone/sgmlop-index.htm) is admittedly non-validating and tolerant: "The *sgmlop* parser is tolerant, and happily accepts XML-like data that are not well-formed. If you need strictness, use another parser." In my own work, I do in fact use a second parser, separating the validation from the processing: 1. I prepare XML documents containing some control characters that are valid only in XML 1.1. I always mark the file 2. I then validate the documents using a Relax NG schema and the Jing validating parser, which knows the difference between XML-1.0-valid and XML-1.1-valid. 3. I then need to "handle" or "process" my already-known-to-be-XML-1.1-valid documents, to map them non-trivially into a different XML 1.1 language. Despite the fact that ElementTree+sgmlop or XIST+sgmlop cannot be "compliant XML 1.1 parsers", their ability to "handle" an already-known-to-be-XML-1.1-valid document is valuable to me, and perhaps to others who want to work with XML 1.1 documents. ****** That was the point of posting the list of "packages handling XML 1.1". If there's a better term than "handle XML 1.1", then please inform me, and I'll try to use it. Ken From Uche.Ogbuji at fourthought.com Mon Sep 5 02:34:54 2005 From: Uche.Ogbuji at fourthought.com (Uche Ogbuji) Date: Sun, 04 Sep 2005 18:34:54 -0600 Subject: [XML-SIG] Corrected list of packages handling XML 1.1 In-Reply-To: <431875D0.6050304@xrce.xerox.com> References: <431875D0.6050304@xrce.xerox.com> Message-ID: <1125880495.15920.31.camel@borgia> On Fri, 2005-09-02 at 17:54 +0200, Ken Beesley wrote: > Uche Ogbuji wrote > > >------------------------------ > > > >Message: 2 > >Date: Thu, 01 Sep 2005 11:59:09 -0600 > >From: Uche Ogbuji > >Subject: Re: [XML-SIG] Corrected list of packages handling XML 1.1 > >To: Walter D?rwald > >Cc: xml-sig at python.org, Ken Beesley > >Message-ID: <1125597549.14255.347.camel at borgia> > >Content-Type: text/plain; charset=ISO-8859-15 > > > >On Thu, 2005-09-01 at 12:50 +0200, Walter D?rwald wrote: > > > > > >>Ken Beesley wrote: > >> > >> > >> > >>>My apologies to Fredrik Lundh of Pythonware for the omission of > >>>ElementType+sgmlop in my recent listing of Python-XML packages that > >>>handle XML 1.1. The list (that I'm aware of) currently includes: 1. > >>>pxdom by Andrew Clover (http://www.doxdesk.com/software/py/pxdom.html, > >>>http://www.doxdesk.com/file/software/py/pxdom.py) 2. pyLTXML from the > >>>Univ. of Edinburgh (http://www.ltg.ed.ac.uk/software/xml, > >>>http://www.ltg.ed.ac.uk/software/gpl_xml.html, > >>>http://www.ltg.ed.ac.uk/software/xml/xmldoc/xmldoc.html) 3. elementtree > >>>library from Pythonware (http://effbot.org/zone/element.htm, > >>>http://effbot.org/zone/element-index.htm) If I've forgotten anyone, > >>>please help me complete the list. > >>> > >>> > >> > [...] > >> > >>XIST (http://www.livinglogic.de/Python/xist) handles XML 1.1 charrefs > >>when a parser is used that does it. (XIST uses sgmlop by default, so it > >>works by default). When serializing XML those charrefs are always > >>supported. See the following snippet: > >> > >> >>> from ll.xist import parsers, presenters > >> >>> from ll.xist.ns import html > >> >>> e = parsers.parseString("this is a backspace: ") > >> >>> print e.asrepr(presenters.CodePresenter()) > >>ll.xist.xsc.Frag( > >> ll.xist.ns.html.body( > >> 'this is a backspace: \x08' > >> ) > >>) > >> >>> print e.asBytes() > >>this is a backspace: > >> > >> > > > >This conversation is really becoming surreal. People, please, it's very > >simple: supporting the range of character references defined in XML 1.1. > >Is not, repeat *NOT* the same thing as being an XML 1.1 parser. > > > >If I have software that parses "b" that does not mean I have an > >XML 1.0 parser. If that software also accepts "b", then it is > >obviously not such. > > > >Any software that accepts "this is a backspace: " > >is neither a compliant XML 1.0 parser nor a compliant XML 1.1. parser. > >All XML 1.1 documents *must have an XML declaration* according to the > >strict stipulation of the spec. If an XML 1.1. parser encounters a > >document without an XML declaration, it *must* assume that it is an XML > >1.0 document, at which point it would *have to* stop with a fatal error > >when it encounters . Period. There is no negotiation here. > > > >Therefore, as far as I can tell, neither the ET/sgmlop trick nor XIST > >are XML 1.1. parsers. I cannot speak for LTXML or pxdom, but knowing > >the authors, I would guess that they are indeed compliant XML 1.1 > >parsers. > > > > > > > > > What Mr. Ogbuji states about "being an XML 1.1 parser" and > "being a compliant XML 1.0 parser [or] a compliant XML 1.1 > parser" is of course correct. However, with respect, I believe > that he misses the point and claims of the list. > > I posted a list of packages "handling XML 1.1", and Martin D?rwald > helpfully added XIST as a package that "handles XML 1.1 charrefs > when a parser [like sgmlop] is used that does it". Neither one of > us claimed that all the listed packages (and especially not the ones > using an underlying sgmlop parser) were "XML 1.1 parsers". Perhaps > my terminology is confusing, but what I meant by "handling XML 1.1" > is this: > > "Handle XML 1.1" = able to process a valid XML 1.1 > document without throwing up and quitting. > > Sgmlop (http://effbot.org/zone/sgmlop-index.htm) is admittedly > non-validating and tolerant: "The *sgmlop* parser is tolerant, and > happily accepts XML-like data that are not well-formed. If you need > strictness, use another parser." > > In my own work, I do in fact use a second parser, separating the > validation from the processing: > > 1. I prepare XML documents containing some control characters that are > valid only in XML 1.1. I always mark the file > > 2. I then validate the documents using a Relax NG schema and the Jing > validating parser, which knows the difference between XML-1.0-valid and > XML-1.1-valid. > > 3. I then need to "handle" or "process" my > already-known-to-be-XML-1.1-valid > documents, to map them non-trivially into a different XML 1.1 language. > Despite the fact that ElementTree+sgmlop or XIST+sgmlop > cannot be "compliant XML 1.1 parsers", their ability to "handle" an > already-known-to-be-XML-1.1-valid document is valuable to me, and perhaps > to others who want to work with XML 1.1 documents. > > ****** > That was the point of posting the list of "packages handling XML 1.1". > If there's a better term than "handle XML 1.1", then please inform me, > and I'll try to use it. Do you really think this hair-splitting will not confuse users? You might as well list grep, emacs, and less in your list because all of these will "process a valid XML 1.1 document without throwing up and quitting". Sheesh. And to think that the point of XML was to avoid such madness in the first place. Think I'm giving you a hard time? You should probably hope that no one in the W3C decides to take your list too seriously. -- Uche Ogbuji Fourthought, Inc. http://uche.ogbuji.net http://fourthought.com http://copia.ogbuji.net http://4Suite.org Use CSS to display XML, part 2 - http://www-128.ibm.com/developerworks/edu/x-dw-x-xmlcss2-i.html XML Output with 4Suite & Amara - http://www.xml.com/pub/a/2005/04/20/py-xml.html Use XSLT to prepare XML for import into OpenOffice Calc - http://www.ibm.com/developerworks/xml/library/x-oocalc/ Schema standardization for top-down semantic transparency - http://www-128.ibm.com/developerworks/xml/library/x-think31.html From fredrik at pythonware.com Mon Sep 5 11:48:43 2005 From: fredrik at pythonware.com (Fredrik Lundh) Date: Mon, 5 Sep 2005 11:48:43 +0200 Subject: [XML-SIG] Corrected list of packages handling XML 1.1 References: <431875D0.6050304@xrce.xerox.com> <1125880495.15920.31.camel@borgia> Message-ID: Uche Ogbuji wrote: > Think I'm giving you a hard time? You should probably hope that no one > in the W3C decides to take your list too seriously. as everyone should have noticed by now, XML is all about lording your XMLiness over others. that's not very Pythonic, of course, and, like or not, this is a Python list. From noreply at sourceforge.net Sun Sep 11 08:01:29 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 10 Sep 2005 23:01:29 -0700 Subject: [XML-SIG] [ pyxml-Patches-1287451 ] xmlproc utf-8 parse fix Message-ID: Patches item #1287451, was opened at 2005-09-11 02:01 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=1287451&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: xmlproc Group: None Status: Open Resolution: None Priority: 5 Submitted By: jlabath (jlabath) Assigned to: Lars Marius Garshol (larsga) Summary: xmlproc utf-8 parse fix Initial Comment: xmlproc will fail with error message: "Character data not allowed outside root element" when parsing utf-8. This will only happen if the utf-8 document actually contains any multibyte characters. After some research i realized that xmlproc/xmlutils.py never changes the length of self.datasize after reencoding the input data. I beleive this patch should solve this problem and should not break anything else, but I have not done extensive testing. Hope this helps. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=306473&aid=1287451&group_id=6473 From nefedova at mcs.anl.gov Wed Sep 14 19:35:24 2005 From: nefedova at mcs.anl.gov (Veronika V. Nefedova) Date: Wed, 14 Sep 2005 12:35:24 -0500 Subject: [XML-SIG] problems with installation Message-ID: <6.0.0.22.2.20050914123146.056a2b10@mail.mcs.anl.gov> Hi, I am trying to install the pyXML package and it seems to have so problems (I use python 2.4.1). Could you please let me know what I am missing here ? I am building it on linux-debian_3.1-ia32 architecture. [64] wiggum /sandbox/nefedova/pyXML/PyXML-0.8.4 > python2.4 setup.py build -v 'import site' failed; use -v for traceback Traceback (most recent call last): File "setup.py", line 7, in ? import sys, os, string ImportError: No module named os Thank you very much, Veronika From fredrik at pythonware.com Wed Sep 14 20:17:21 2005 From: fredrik at pythonware.com (Fredrik Lundh) Date: Wed, 14 Sep 2005 20:17:21 +0200 Subject: [XML-SIG] problems with installation References: <6.0.0.22.2.20050914123146.056a2b10@mail.mcs.anl.gov> Message-ID: Veronika V. Nefedova wrote: > I am trying to install the pyXML package and it seems to have so problems > (I use python 2.4.1). Could you please let me know what I am missing here ? > I am building it on linux-debian_3.1-ia32 architecture. > > [64] wiggum /sandbox/nefedova/pyXML/PyXML-0.8.4 > python2.4 setup.py build -v > 'import site' failed; use -v for traceback > Traceback (most recent call last): > File "setup.py", line 7, in ? > import sys, os, string > ImportError: No module named os "import site failed" followed by more import failures means that your Python installation is seriously broken. what happens if you just start the interpreter? $ python2.4 From tom at holotrope.com Sun Sep 18 05:17:51 2005 From: tom at holotrope.com (Tom Howard) Date: Sat, 17 Sep 2005 22:17:51 -0500 Subject: [XML-SIG] Install error Message-ID: When installing PyXML-0.8.4 from the Terminal window I get an error at the end: error: /System/Library/Frameworks/Python.framework/Versions/2.3/bin/xmlproc_parse: Permission denied I?m not sure how to get around this or how to add my username/password to the install command. Any help is greatly appreciated! Thanks! Tom Howard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/xml-sig/attachments/20050917/c0e17695/attachment.htm From fredrik at pythonware.com Mon Sep 19 18:29:28 2005 From: fredrik at pythonware.com (Fredrik Lundh) Date: Mon, 19 Sep 2005 18:29:28 +0200 Subject: [XML-SIG] Install error References: Message-ID: Tom Howard wrote: > When installing PyXML-0.8.4 from the Terminal window I get an error at the > end: > > error: > /System/Library/Frameworks/Python.framework/Versions/2.3/bin/xmlproc_parse: >Permission denied > > I'm not sure how to get around this or how to add my username/password to > the install command. the usual Unix way is to log in as the correct user *before* you run the installation command. From sesquile at gmail.com Wed Sep 21 02:16:28 2005 From: sesquile at gmail.com (m h) Date: Tue, 20 Sep 2005 17:16:28 -0700 Subject: [XML-SIG] Diff for wddx.py for comment and null support Message-ID: Hello all- I just joined the list. I recently (today) had to parse WDDX in python. In order to get it to work I had to patch wddx.py accordingly: 197,198d196 < 'comment': (None, None), < 'null': ('um_start_null', 'um_end_null'), 212,216d209 < def um_start_null(self, name, attr): < pass < def um_end_null(self, name): < self.data_stack.append(None) < Don't know if anyone else is using wddx or even interested, but I thought I'd share the diff. matt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/xml-sig/attachments/20050920/acbd1777/attachment.html From delatinlane at cs.com Mon Sep 26 16:51:27 2005 From: delatinlane at cs.com (delatinlane@cs.com) Date: Mon, 26 Sep 2005 10:51:27 -0400 Subject: [XML-SIG] Mail System Error - Returned Mail Message-ID: <20050926145137.4BD731E4002@bag.python.org> Your message was undeliverable due to the following reason: Your message could not be delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message could not be delivered within 5 days: Host 198.86.156.53 is not responding. The following recipients did not receive this message: Please reply to postmaster at python.org if you feel this message to be in error. -------------- next part -------------- A non-text attachment was scrubbed... Name: message.zip Type: application/octet-stream Size: 26265 bytes Desc: not available Url : http://mail.python.org/pipermail/xml-sig/attachments/20050926/51c33873/message-0001.obj