inspect.getargvalues fails if arg name is not bound to a value

Open
#61,448 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

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

3.13 3.14 3.15 easy stdlib triaged type-bug
BPO 17246
Nosy @ezio-melotti, @iritkatriel, @macgors
Files
  • test_cgitb.py: Short script demonstrating the problem
  • issue17246.diff: Proof of concept against 2.7.
  • 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

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.