Just a question about the element tree API: do you feel it could evolve a bit in new versions? Here are a few suggestions (that would help me, yes, when making XPath requests on dynamically created elements, but which could be useful anyway):
* Requesting children that have a specific tag and/or a specific attributes with (optional) values. Today the XPath engine goes though all children, then pick the right ones. If the XPath engine used this function, that would allow it to be used in a situation where you have thousands of (virtual until instantiated) Elements, if the XPath request is properly written.
* Having a "parent" (python) attribute in each node, so that you don't need to have a map to go one level higher in the hierarchy.
Just a question about the element tree API: do you feel it could evolve a bit in new versions? Here are a few suggestions (that would help me, yes, when making XPath requests on dynamically created elements, but which could be useful anyway):
* Requesting children that have a specific tag and/or a specific attributes with (optional) values. Today the XPath engine goes though all children, then pick the right ones. If the XPath engine used this function, that would allow it to be used in a situation where you have thousands of (virtual until instantiated) Elements, if the XPath request is properly written.
* Having a "parent" (python) attribute in each node, so that you don't need to have a map to go one level higher in the hierarchy.