Python 3.2 supports ElementPath version 1.3. The relevant documentation is
http://effbot.org/zone/element-xpath.htm. It says:
..	(New in 1.3) Selects the parent element.

However, a CHANGES document says:
The engine also provides limited support for the ".." parent operator; you can use it inside the subtree, but it cannot go above the target element (the element you called "find" on).  

The normal documentation should document the limitation.

Here is a link to our docs page with the info that needs to be changed:

http://docs.python.org/py3k/library/xml.etree.elementtree.html#supported-xpath-syntax

I was going to work on a patch but in irc we decided to wait to see what people had to say about this. Also we think documenting the Error you receive (if any) when trying to go above the "found" element may be a necessary part of the doc change.

Thanks for the report, Patrick. Yes, documenting this limitation would make sense. Have you tested to see how it behaves?

Anyhow, a patch would be welcome ;-)

It doesn't look like there are any errors to document. I'm attaching a patch that Patrick suggested.

To be complete: an xpath 'above' the start element returns None

Thanks for the patch!

In response to patrick vrijlandt last comment here's a patch. I also found a few None keywords that didn't have `` around them.

New changeset 79231a12567a by Eli Bendersky in branch '3.3':
Issue #12322: clarify xpath reference for cases where the path reaches ancestors of the start element. Also add missing markup for a None. Thanks to patrick vrijlandt and Mike Hoy for the report and initial patches.
http://hg.python.org/cpython/rev/79231a12567a

New changeset 5cb3c08997e6 by Eli Bendersky in branch 'default':
Merge 3.3
http://hg.python.org/cpython/rev/5cb3c08997e6

Changes pushed. Thanks for the report and patches.

Mike - a note for the future: when you create an updated patch, create it anew vs. a clean repo. Don't "compound" patches.

>> Mike - a note for the future: when you create an updated patch, create it anew vs. a clean repo. Don't "compound" patches.

No problem, thanks for committing the patch. Wasn't aware that compounding patches caused a problem.