On Tue, Nov 26, 2013 at 9:45 AM, Larry Martell <larry.mart...@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. >> 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@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. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
