A better way to resolve ForwardRefs in type aliases across modules
Open
Nobody has claimed this yet.
3.11
stdlib
topic-typing
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 46371 |
|---|---|
| Nosy | @gvanrossum, @JelleZijlstra, @sobolevn, @Fidget-Spinner, @kumaraditya303, @AlexWaygood, @aha79 |
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 2022-01-13.23:48:15.238>
labels = ['type-feature', 'library', '3.11']
title = 'A better way to resolve ForwardRefs in type aliases across modules'
updated_at = <Date 2022-01-14.07:31:01.351>
user = 'https://github.com/aha79'
bugs.python.org fields:
activity = <Date 2022-01-14.07:31:01.351>
actor = 'AlexWaygood'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2022-01-13.23:48:15.238>
creator = 'andreash'
dependencies = []
files = []
hgrepos = []
issue_num = 46371
keywords = []
message_count = 1.0
messages = ['410535']
nosy_count = 7.0
nosy_names = ['gvanrossum', 'JelleZijlstra', 'sobolevn', 'kj', 'kumaraditya', 'AlexWaygood', 'andreash']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46371'
versions = ['Python 3.11']
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 with migrated BPO issue 46371 and review its single recorded comment for the original discussion. The payload names no files, tests, entry points, or acceptance criteria, so the desired implementation and definition of done still need to be established before coding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100