Patrick W. p...@borntolaugh.de added the comment:
Nick Coghlan (ncoghlan) at 2010-12-29 08:46 (UTC):
No, the context must always be included unless explicitly suppressed.
Then there should be some actually working way to suppress it, right?
I think the standard behaviour that automatically
Patrick W. p...@borntolaugh.de added the comment:
Antoine Pitrou (pitrou) at 2010-12-30 18:32 (UTC)
We are talking about context, not cause.
Yes, but - as said before - obviously the cause takes a higher precedence than
context (otherwise it wouldn't show a context message when you
Patrick W. p...@borntolaugh.de added the comment:
Thanks for your reply, Amaury. That page really might mean that it was not
intended for ElementTree to parse such things by default. Although it might be
nice if there was some easy way to simply enable it, instead of having to hack
New submission from Patrick W. p...@borntolaugh.de:
When using xml.etree.ElementTree to parse external XML files, all XML comments
within that file are being stripped out. I guess that happens because there is
no comment handler in the expat parser.
Example:
test.xml
example
nodeA
New submission from Patrick W. p...@borntolaugh.de:
I'm currently writing a library that executes predefined http requests
to a specified server. In case there is for example a HTTP Error, I want
to raise a user-defined exception that contains additional information
about when the error actually
