Strange XPath search behavior of xml.etree.ElementTree.Element.find
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
topic-XML
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42893 |
|---|---|
| Nosy | @scoder, @tiran |
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:
assignee = None
closed_at = None
created_at = <Date 2021-01-11.17:12:45.685>
labels = ['3.8', 'type-bug', 'library']
title = 'Strange XPath search behavior of xml.etree.ElementTree.Element.find'
updated_at = <Date 2021-01-15.01:53:49.825>
user = 'https://bugs.python.org/robpats'
bugs.python.org fields:
activity = <Date 2021-01-15.01:53:49.825>
actor = 'robpats'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-01-11.17:12:45.685>
creator = 'robpats'
dependencies = []
files = []
hgrepos = []
issue_num = 42893
keywords = []
message_count = 3.0
messages = ['384851', '385011', '385094']
nosy_count = 3.0
nosy_names = ['scoder', 'christian.heimes', 'robpats']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42893'
versions = ['Python 3.8']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies xml.etree.ElementTree.Element.find as the entry point but provides no reproduction, implementation file, or test. First reproduce the XPath behavior and establish the expected result, then locate the relevant ElementTree code and add regression coverage; done means the agreed behavior is captured by a passing test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100