Add suggestion about keyword arguments to this error message: "builtins.TypeError: my_func() takes 1 positional argument but 2 were given"
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reviewing the linked issue22652.patch and the original issue22652 discussion to understand the proposed wording and the interpreter behavior it targets. Done means adding a useful keyword-argument suggestion to this TypeError message while preserving the existing error behavior.
Written by the indexing model from the issue text.
Description
| BPO | 22652 |
|---|---|
| Nosy | @terryjreedy, @bitdancer, @cool-RR, @serhiy-storchaka, @ztane, @ajdavis |
| Files |
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-10-16.10:33:37.182>
labels = ['interpreter-core', 'type-feature', '3.9']
title = 'Add suggestion about keyword arguments to this error message: "builtins.TypeError: my_func() takes 1 positional argument but 2 were given"'
updated_at = <Date 2020-05-15.15:07:20.596>
user = 'https://github.com/cool-RR'
bugs.python.org fields:
activity = <Date 2020-05-15.15:07:20.596>
actor = 'emptysquare'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2014-10-16.10:33:37.182>
creator = 'cool-RR'
dependencies = []
files = ['38929']
hgrepos = []
issue_num = 22652
keywords = ['patch']
message_count = 10.0
messages = ['229521', '229522', '240541', '240553', '240558', '240655', '368878', '368880', '368940', '368951']
nosy_count = 6.0
nosy_names = ['terry.reedy', 'r.david.murray', 'cool-RR', 'serhiy.storchaka', 'ztane', 'emptysquare']
pr_nums = []
priority = 'low'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue22652'
versions = ['Python 3.9']
- 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 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100