search

python / cpython

The Python programming language
https://www.python.org
Other
62.39k stars 29.96k forks source link

xml.etree sourcecode bug #74637

Closed 23004c14-65ff-496c-bf6b-b710dc617c7e closed 7 years ago

23004c14-65ff-496c-bf6b-b710dc617c7e commented 7 years ago
BPO 30452
Nosy @serhiy-storchaka
Files
  • xmlMerge.py: xml merger
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields: ```python assignee = None closed_at = created_at = labels = ['expert-XML', 'invalid'] title = 'xml.etree sourcecode bug' updated_at = user = 'https://bugs.python.org/baksaz' ``` bugs.python.org fields: ```python activity = actor = 'serhiy.storchaka' assignee = 'none' closed = True closed_date = closer = 'serhiy.storchaka' components = ['XML'] creation = creator = 'baksaz' dependencies = [] files = ['46891'] hgrepos = [] issue_num = 30452 keywords = [] message_count = 3.0 messages = ['294335', '294349', '294471'] nosy_count = 2.0 nosy_names = ['serhiy.storchaka', 'baksaz'] pr_nums = [] priority = 'normal' resolution = 'not a bug' stage = 'resolved' status = 'closed' superseder = None type = None url = 'https://bugs.python.org/issue30452' versions = ['Python 3.6'] ```

    23004c14-65ff-496c-bf6b-b710dc617c7e commented 7 years ago

    Hi, I used before an XML merger script with 2.7 version, which was running fine. After my Anaconda was updated by SCCM to version 3.6 the same script fails and reports the following traceback:

    File "C:\Program Files\Anaconda3\lib\xml\etree\ElementTree.py", line 1190, in parse tree.parse(source, parser) File "C:\Program Files\Anaconda3\lib\xml\etree\ElementTree.py", line 591, in p arse self._root = parser._parse_whole(source) xml.etree.ElementTree.ParseError: unclosed token: line 128, column 4

    What can I do?

    23004c14-65ff-496c-bf6b-b710dc617c7e commented 7 years ago

    The error was caused, because the xml files did not had the correct close element for the root tag. The issue is not closed, because the error message was not adequate to be able to highlight the root cause.

    serhiy-storchaka commented 7 years ago

    This error message is not created by xml.etree, it is just propagated from the expat library. Open a ticket on the expat library tracker if you want to improve the error message.