improve TypeError messages for missing arguments (meta issue)

Open
#60,747 23 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

This is a meta issue rather than a self-contained change. Start by reviewing the task issues 60719, 60724, and 66842; issues 59406 and 60194 are marked complete. Done means the remaining missing-argument TypeError message tasks have been resolved.

Written by the indexing model from the issue text.

Description

3.10 3.9 (EOL) interpreter-core type-feature
BPO 16543
Nosy @terryjreedy, @mdickinson, @ezio-melotti, @merwok, @cjerdonek, @serhiy-storchaka
Files
  • unpacktuple.diff: Patch against 3.2.
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Tasks
    Show more details

    GitHub fields:

    assignee = None
closed_at = None
created_at = <Date 2012-11-23.18:03:13.251>
labels = ['interpreter-core', 'type-feature', '3.9', '3.10']
title = 'improve TypeError messages for missing arguments (meta issue)'
updated_at = <Date 2020-11-15.18:56:08.110>
user = 'https://github.com/ezio-melotti'

    bugs.python.org fields:

    activity = <Date 2020-11-15.18:56:08.110>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2012-11-23.18:03:13.251>
creator = 'ezio.melotti'
dependencies = []
files = ['28090']
hgrepos = []
issue_num = 16543
keywords = ['patch']
message_count = 22.0
messages = ['176202', '176205', '176207', '176208', '176209', '176210', '176212', '176213', '176218', '176223', '176226', '176229', '176230', '176232', '176234', '176236', '176237', '176241', '176243', '176314', '176372', '176397']
nosy_count = 6.0
nosy_names = ['terry.reedy', 'mark.dickinson', 'ezio.melotti', 'eric.araujo', 'chris.jerdonek', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue16543'
versions = ['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.