inspect.getargvalues fails if arg name is not bound to a value
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 30/100
Research direction
Start with inspect.getargvalues and the referenced test_cgitb.py script to reproduce the failure when an argument name is not bound. Review the linked issue17246.diff and existing discussion before changing behavior. Done means the failure is covered by a regression test and the expected handling of an unbound argument is established.
Written by the indexing model from the issue text.
Description
| BPO | 17246 |
|---|---|
| Nosy | @ezio-melotti, @iritkatriel, @macgors |
| 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 2013-02-19.22:22:36.701>
labels = ['easy', 'type-bug', '3.9', '3.10', '3.11', 'library']
title = 'inspect.getargvalues fails if arg name is not bound to a value'
updated_at = <Date 2022-03-29.18:46:57.608>
user = 'https://bugs.python.org/AndrewLutomirski'
bugs.python.org fields:
activity = <Date 2022-03-29.18:46:57.608>
actor = 'macgors'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-02-19.22:22:36.701>
creator = 'Andrew.Lutomirski'
dependencies = []
files = ['29125', '29166']
hgrepos = []
issue_num = 17246
keywords = ['easy']
message_count = 4.0
messages = ['182446', '182705', '396039', '416283']
nosy_count = 4.0
nosy_names = ['ezio.melotti', 'Andrew.Lutomirski', 'iritkatriel', 'macgors']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue17246'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
Linked PRs
- gh-101318
- gh-144854
- 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
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
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