[issue18304] ElementTree gets awkward to use if there is an xmlns

2013-08-11 Thread Bryce Nesbitt
Bryce Nesbitt added the comment: The mere existence of popular solutions like 'item.tag.split("}")[1][0:]' argues something is wrong. What could lmxl do to make this cleaner (even if the ticket proposal is junk). -- title: ElementTree -- provide a way to ignore namespace in tags and sea

[issue18304] ElementTree gets awkward to use if there is an xmlns

2013-08-11 Thread Stefan Behnel
Stefan Behnel added the comment: FWIW, lxml.etree supports wildcards like '{*}tag' in searches, and this is otherwise quite rarely a problem in practice. I'm -1 on the proposed feature and wouldn't mind rejecting this all together. (At least change the title to something more appropriate.) --

[issue18304] ElementTree gets awkward to use if there is an xmlns

2013-06-25 Thread Bryce Nesbitt
New submission from Bryce Nesbitt: ElementTree offers a wonderful and easy API for parsing XML... but if there is a namespace involved it suddenly gets ugly. This is a proposal to fix that. First an example: -- !/usr/bin/python # Demonstrate awkward behavior of namespaces in