Constructor signature is duplicated in the help of namedtuples
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 30959 |
|---|---|
| Nosy | @rhettinger, @ncoghlan, @serhiy-storchaka, @SylvainDe |
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 2017-07-18.11:04:22.806>
labels = ['3.7', 'type-bug', 'library']
title = 'Constructor signature is duplicated in the help of namedtuples'
updated_at = <Date 2017-07-21.08:54:23.446>
user = 'https://github.com/serhiy-storchaka'
bugs.python.org fields:
activity = <Date 2017-07-21.08:54:23.446>
actor = 'SylvainDe'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-07-18.11:04:22.806>
creator = 'serhiy.storchaka'
dependencies = []
files = []
hgrepos = []
issue_num = 30959
keywords = []
message_count = 3.0
messages = ['298582', '298766', '298784']
nosy_count = 4.0
nosy_names = ['rhettinger', 'ncoghlan', 'serhiy.storchaka', 'SylvainDe']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue30959'
versions = ['Python 3.7']
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 reproducing the duplicated constructor signature in the help output for namedtuples and locate the standard-library implementation responsible. Confirm the corrected help output no longer repeats the constructor signature, then add or update a focused regression test if the relevant test location is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100