Modify XML parsing library descriptions to forewarn of content loss hazard
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
docs
topic-XML
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43561 |
|---|---|
| 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:52:35.411>
labels = ['3.7', '3.8', '3.9', 'docs']
title = 'Modify XML parsing library descriptions to forewarn of content loss hazard'
updated_at = <Date 2021-03-19.18:52:35.411>
user = 'https://github.com/ridgerat'
bugs.python.org fields:
activity = <Date 2021-03-19.18:52:35.411>
actor = 'ridgerat1611'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2021-03-19.18:52:35.411>
creator = 'ridgerat1611'
dependencies = []
files = []
hgrepos = []
issue_num = 43561
keywords = []
message_count = 1.0
messages = ['389111']
nosy_count = 2.0
nosy_names = ['docs@python', 'ridgerat1611']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue43561'
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
No source files or tests are named. Start by locating the XML parsing library descriptions in the Python documentation and review the content-loss hazard described by BPO 43561; done means the relevant descriptions clearly warn readers about that hazard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100