Cross-module dataclass inheritance breaks get_type_hints
Ouverte
@ericvsmith y travaille déjà.
Depuis le 30/11/2021.
3.10
3.11
3.9 (EOL)
stdlib
topic-dataclasses
topic-typing
type-bug
- Langage dominant
- Python
- Étoiles
- 77.2k
- Forks
- 36k
- Métriques de merge des PR
- Métriques de PR en attente
Description
| BPO | 45524 |
|---|---|
| Nosy | @gvanrossum, @ericvsmith, @JelleZijlstra, @sobolevn, @Fidget-Spinner, @AlexWaygood |
| PRs |
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
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Évaluation
Cette issue n'a pas encore été évaluée.