[issue18753] [c]ElementTree.fromstring fails to parse ]]>

R. David Murray added the comment: Not a problem, these things are often subtle. And now there is a record of it in the tracker if anyone else questions it in the future. -- stage: -> committed/rejected ___ Python tracker

[issue18753] [c]ElementTree.fromstring fails to parse ]]>

Changes by Kees Bos : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue18753] [c]ElementTree.fromstring fails to parse ]]>

Kees Bos added the comment: OK. I got clarification from the lxml list. It's not a bug. And it's sepcified in section 2.4 (http://www.w3.org/TR/REC-xml/#syntax): The ampersand character (&) and the left angle bracket (<) MUST NOT appear in their literal form, except when used as markup delimit

[issue18753] [c]ElementTree.fromstring fails to parse ]]>

Changes by Antoine Pitrou : -- nosy: +eli.bendersky, scoder ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue18753] [c]ElementTree.fromstring fails to parse ]]>

Kees Bos added the comment: I'm not an expert, but from: http://www.w3.org/TR/REC-xml/#NT-AttValue AttValue ::= '"' ([^<&"] | Reference)* '"' | "'" ([^<&'] | Reference)* "'" which I read as: Any Reference character is valid, except & and <, which are used for escaping and closing the

[issue18753] [c]ElementTree.fromstring fails to parse ]]>

R. David Murray added the comment: Why do you think this is a bug? (You may well be right; I'm not familiar with the intricacies of XML. But on its face the behavior looks reasonable.) -- nosy: +r.david.murray ___ Python tracker

[issue18753] [c]ElementTree.fromstring fails to parse ]]>

New submission from Kees Bos: ElementTree.fromstring and cElementTree.fromstring fail on parsing "]]>", but do parse "]]>" $ python Python 2.7.3 (default, Apr 10 2013, 05:09:49) [GCC 4.7.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from xml.etree impor