Comment 1 for bug 1195141
Revision history for this message
| Thomi Richards (thomir-deactivatedaccount) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I started working on this today, and then realised that we cannot complete this work unless we extend the xpathselect wire protocol. The reason is simple: there's no restriction that says that each object in the tree must occupy a unique path within the tree, so there's no way, given a child path string, to get a path that is guaranteed to select the child's parent.
@Leo, how critical is this? It wouldn't be hard to add to xpathselect, but these updates to the xpathselect language are rather burdensome... so I'd rather bundle it together with other changes in the future, if at all possible.