help() module listing displays import warnings from deprecated package modules
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
Start by reproducing the help() module listing described in the issue and inspect where the import warnings from deprecated package modules originate. Identify the affected library or documentation entry points, then verify that the module listing no longer displays those warnings while still showing the expected modules.
Written by the indexing model from the issue text.
Description
| BPO | 44215 |
|---|---|
| Nosy | @stefanor |
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-05-23.12:18:27.045>
labels = ['type-bug', '3.9', '3.10', '3.11', 'library', 'docs']
title = 'help() module listing displays import warnings from deprecated package modules'
updated_at = <Date 2021-05-28.19:26:51.626>
user = 'https://github.com/stefanor'
bugs.python.org fields:
activity = <Date 2021-05-28.19:26:51.626>
actor = 'terry.reedy'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)']
creation = <Date 2021-05-23.12:18:27.045>
creator = 'stefanor'
dependencies = []
files = []
hgrepos = []
issue_num = 44215
keywords = []
message_count = 1.0
messages = ['394196']
nosy_count = 2.0
nosy_names = ['docs@python', 'stefanor']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44215'
versions = ['Python 3.9', 'Python 3.10', '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 ·