Pydoc: add option to remove run-specific ids (addresses)
Open
Nobody has claimed this yet.
3.9 (EOL)
docs
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39391 |
|---|---|
| Nosy | @terryjreedy, @asvetlov, @serhiy-storchaka, @ammaraskar |
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-19.23:03:57.467>
labels = ['type-feature', '3.9', 'docs']
title = 'Pydoc: add option to remove run-specific ids (addresses)'
updated_at = <Date 2020-02-01.19:38:02.564>
user = 'https://bugs.python.org/peteroupc'
bugs.python.org fields:
activity = <Date 2020-02-01.19:38:02.564>
actor = 'terry.reedy'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2020-01-19.23:03:57.467>
creator = 'peteroupc'
dependencies = []
files = []
hgrepos = []
issue_num = 39391
keywords = []
message_count = 9.0
messages = ['360278', '360593', '360600', '360819', '360842', '360843', '361128', '361151', '361188']
nosy_count = 6.0
nosy_names = ['terry.reedy', 'asvetlov', 'docs@python', 'serhiy.storchaka', 'ammar2', 'peteroupc']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue39391'
versions = ['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
The issue names Pydoc but no implementation file or test. Start by locating Pydoc's option entry point and determining how run-specific IDs (addresses) appear in generated output; done means an option removes them and tests cover the resulting stable output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100