Modify SAX/expat parsing to avoid fragmentation of already-tiny content chunks
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
topic-XML
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43560 |
|---|---|
| Nosy | @ridgerat |
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-03-19.18:39:18.829>
labels = ['expert-XML', '3.8', 'type-feature', '3.7', '3.9']
title = 'Modify SAX/expat parsing to avoid fragmentation of already-tiny content chunks'
updated_at = <Date 2021-03-19.18:39:18.829>
user = 'https://github.com/ridgerat'
bugs.python.org fields:
activity = <Date 2021-03-19.18:39:18.829>
actor = 'ridgerat1611'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['XML']
creation = <Date 2021-03-19.18:39:18.829>
creator = 'ridgerat1611'
dependencies = []
files = []
hgrepos = []
issue_num = 43560
keywords = []
message_count = 1.0
messages = ['389108']
nosy_count = 1.0
nosy_names = ['ridgerat1611']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue43560'
versions = ['Python 3.7', 'Python 3.8', 'Python 3.9']
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
Start by locating CPython's SAX/expat XML parsing implementation and inspect how already-tiny content chunks are emitted. Confirm the current fragmentation behavior and define done as preserving those tiny chunks without further fragmentation, with focused coverage for the affected parsing path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100