parsing nested unbounded XML fields with ElementTree

[Larry Martell]

On Mon, Nov 25, 2013 at 6:19 PM, Chris Angelico <rosuav at gmail.com> wrote:

> On Tue, Nov 26, 2013 at 9:45 AM, Larry Martell <larry.martell at gmail.com>
> wrote:
> > On Monday, November 25, 2013 5:30:44 PM UTC-5, Chris Angelico wrote:
> >
> >> First off, please clarify: Are there five corresponding </Node> tags
> >> later on? If not, it's not XML, and nesting will have to be defined
> >> some other way.
> >
> > Yes, there are corresponding </Node> tags. I just didn't show them.
>
> Good good, I just saw the "unbounded" in your subject line and got
> worried :) I'm pretty sure there's a way to parse that will preserve
> the current nesting information, but others can describe that better
> than I can.
>

The term 'unbounded' is used in the XML xsd file like this:

<xs:sequence maxOccurs="unbounded">


> >> Secondly, please get off Google Groups. Your initial post is
> >> malformed, and unless you specifically fight the software, your
> >> replies will be even more malformed, to the point of being quite
> >> annoying. There are many other ways to read a newsgroup, or you can
> >> subscribe to the mailing list python-list at python.org, which carries
> >> the same content.
> >
> > Not sure what you mean by malformed. I don't really care for Google
> Groups,
> > but I've been using it to post to this any other groups for years (since
> rn
> > and deja news went away) and no one ever said my posts were malformed. In
> > any case, I did not know the group was available as a ML. I've subbed to
> > that and will post that way.
>
> The mailing list works well for me too. Google Groups is deceptively
> easy for a lot of people, but if you look through the list's archives,
> you'll see that the posts it makes are unwrapped (and thus string out
> to the right an arbitrary length), and all quoted text is
> double-spaced, among other problems. Its users are generally unaware
> of this, and like you are not maliciously inflicting that on us all,
> but that doesn't make it any less painful to read :) Thanks for
> switching.
>
>
I had noticed the double spacing and I always fixed that when I replied.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20131125/1358e671/attachment.html>