expat parser not xml 1.1 compliant (breaks xmlrpclib) - still
Open
Nobody has claimed this yet.
topic-XML
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39512 |
|---|---|
| Nosy | @terryjreedy |
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 2020-01-31.18:26:08.418>
labels = ['expert-XML']
title = 'expat parser not xml 1.1 compliant (breaks xmlrpclib) - still'
updated_at = <Date 2020-02-09.19:48:49.160>
user = 'https://bugs.python.org/mforkel'
bugs.python.org fields:
activity = <Date 2020-02-09.19:48:49.160>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['XML']
creation = <Date 2020-01-31.18:26:08.418>
creator = 'mforkel'
dependencies = []
files = []
hgrepos = []
issue_num = 39512
keywords = []
message_count = 2.0
messages = ['361124', '361660']
nosy_count = 3.0
nosy_names = ['terry.reedy', 'scode', 'mforkel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue39512'
versions = []
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
No source file or test is named. Start by reading the migrated report for BPO issue 39512 and the two linked messages, then trace the expat parser behavior used by xmlrpclib. Done means establishing XML 1.1 compliance and confirming that the reported xmlrpclib breakage is resolved with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100