Docs: mark deprecated items in the TOC
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
The issue names no files or tests. Start by locating the documentation tables of contents and identifying the deprecated items they contain; done means those items are visibly marked in the TOC and the rendered documentation reflects the change.
Written by the indexing model from the issue text.
Description
| BPO | 20393 |
|---|---|
| Nosy | @birkenfeld, @ezio-melotti |
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 2014-01-25.21:29:29.554>
labels = ['3.11', 'type-feature', 'docs']
title = 'Docs: mark deprecated items in the TOC'
updated_at = <Date 2021-06-02.14:16:45.027>
user = 'https://bugs.python.org/zearin'
bugs.python.org fields:
activity = <Date 2021-06-02.14:16:45.027>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2014-01-25.21:29:29.554>
creator = 'zearin'
dependencies = []
files = []
hgrepos = []
issue_num = 20393
keywords = []
message_count = 2.0
messages = ['209239', '211282']
nosy_count = 4.0
nosy_names = ['georg.brandl', 'ezio.melotti', 'docs@python', 'zearin']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue20393'
versions = ['Python 3.11']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·