python / python/cpython

Cross-module dataclass inheritance breaks get_type_hints

Open
#89,687 28 comments 1 reaction 1 assignee View on GitHub

@ericvsmith is already working on this.

Since Nov 30, 2021.

3.10 3.11 3.9 (EOL) stdlib topic-dataclasses topic-typing type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 45524
Nosy @gvanrossum, @ericvsmith, @JelleZijlstra, @sobolevn, @Fidget-Spinner, @AlexWaygood
PRs
  • python/cpython#29158
  • 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 = 'https://github.com/ericvsmith'
    closed_at = None
    created_at = <Date 2021-10-19.14:37:47.448>
    labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
    title = 'Cross-module dataclass inheritance breaks get_type_hints'
    updated_at = <Date 2022-01-22.08:37:13.515>
    user = 'https://bugs.python.org/aidanbclark'
    

    bugs.python.org fields:

    activity = <Date 2022-01-22.08:37:13.515>
    actor = 'AlexWaygood'
    assignee = 'eric.smith'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2021-10-19.14:37:47.448>
    creator = 'aidan.b.clark'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 45524
    keywords = ['patch']
    message_count = 13.0
    messages = ['404307', '404312', '404313', '404314', '404321', '404740', '404752', '404754', '404812', '404822', '404823', '404907', '404918']
    nosy_count = 8.0
    nosy_names = ['gvanrossum', 'eric.smith', 'JelleZijlstra', 'slebedev', 'sobolevn', 'kj', 'AlexWaygood', 'aidan.b.clark']
    pr_nums = ['29158']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue45524'
    versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
    

    Linked PRs
    • gh-137168

    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.

    Assessment

    This issue has not been assessed yet.

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.