TypeError message incorrect for max() with one keyword arg

Open
#60,719 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start by reading issue16515.diff and issue16515-unpacktuple.diff, then trace the max() argument-handling path and PyArg_UnpackTuple entry point in CPython. Compare the current TypeError wording with the issue's stated problem and validate the correction against related interpreter behavior. Done means the one-keyword-argument max() case reports the correct message without regressing missing-argument messages.

Written by the indexing model from the issue text.

Description

interpreter-core type-bug
BPO 16515
Nosy @mdickinson, @ezio-melotti, @cjerdonek
Dependencies
  • bpo-16543: improve TypeError messages for missing arguments (meta issue)
    		•
    Files
  • issue16515.diff: Patch against 3.2.
  • issue16515-unpacktuple.diff: Patch against 3.2 to fix the message in PyArg_UnpackTuple.
    		•

    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 2012-11-20.22:36:57.084>
labels = ['interpreter-core', 'type-bug', '3.8', '3.9', '3.10']
title = 'TypeError message incorrect for max() with one keyword arg'
updated_at = <Date 2020-10-22.18:35:07.206>
user = 'https://github.com/cjerdonek'

    bugs.python.org fields:

    activity = <Date 2020-10-22.18:35:07.206>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2012-11-20.22:36:57.084>
creator = 'chris.jerdonek'
dependencies = ['16543']
files = ['28064', '28065']
hgrepos = []
issue_num = 16515
keywords = ['patch']
message_count = 7.0
messages = ['176034', '176044', '176063', '176067', '176068', '176070', '176204']
nosy_count = 3.0
nosy_names = ['mark.dickinson', 'ezio.melotti', 'chris.jerdonek']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue16515'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

    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.