from __future__ import annotations breaks profiler's handling of dataclasses
Open
Nobody has claimed this yet.
3.11
3.12
3.13
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44414 |
|---|---|
| Nosy | @JelleZijlstra, @wilcoxjay |
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 2021-06-13.21:20:30.284>
labels = ['type-bug', 'library', '3.9']
title = "from __future__ import annotations breaks profiler's handling of dataclasses"
updated_at = <Date 2021-06-14.04:51:07.905>
user = 'https://github.com/wilcoxjay'
bugs.python.org fields:
activity = <Date 2021-06-14.04:51:07.905>
actor = 'JelleZijlstra'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-06-13.21:20:30.284>
creator = 'wilcoxjay'
dependencies = []
files = []
hgrepos = []
issue_num = 44414
keywords = []
message_count = 1.0
messages = ['395762']
nosy_count = 2.0
nosy_names = ['JelleZijlstra', 'wilcoxjay']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44414'
versions = ['Python 3.9']
Linked PRs
- gh-155600
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the profiler and dataclasses behavior described in the issue, then inspect linked PR gh-155600 for the current direction. Confirm the failure with a focused reproduction using from future import annotations and dataclasses; done means profiler handling works correctly without regressing existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100