Make builtins.callable "generic"

Open
#86,268 15 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

The payload names no files or tests; start by reviewing PR #22848 and the linked BPO-42102 discussion to recover the intended meaning of “generic” for builtins.callable. Done means implementing the agreed behavior and validating it with the tests identified during that review.

Written by the indexing model from the issue text.

Description

topic-typing type-feature
BPO 42102
Nosy @gvanrossum, @serhiy-storchaka, @ilevkivskyi, @isidentical, @hauntsaninja, @Fidget-Spinner
PRs
  • python/cpython#22848
  • 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 2020-10-20.21:48:49.801>
    labels = ['type-feature', '3.10']
    title = 'Make builtins.callable "generic"'
    updated_at = <Date 2020-11-23.15:19:16.522>
    user = 'https://github.com/hauntsaninja'
    

    bugs.python.org fields:

    activity = <Date 2020-11-23.15:19:16.522>
    actor = 'gvanrossum'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = []
    creation = <Date 2020-10-20.21:48:49.801>
    creator = 'hauntsaninja'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 42102
    keywords = ['patch']
    message_count = 15.0
    messages = ['379169', '379179', '379182', '379196', '379197', '381072', '381080', '381081', '381141', '381151', '381155', '381158', '381641', '381657', '381671']
    nosy_count = 6.0
    nosy_names = ['gvanrossum', 'serhiy.storchaka', 'levkivskyi', 'BTaskaya', 'hauntsaninja', 'kj']
    pr_nums = ['22848']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue42102'
    versions = ['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.