TypedDict and NamedTuple do not evaluate cross-module ForwardRef in all cases

Open
#90,531 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start with the standard-library typing implementation for TypedDict and NamedTuple and reproduce the cross-module ForwardRef cases described in the issue. Inspect the existing tests for these features and add regression coverage; done means the relevant ForwardRef cases evaluate consistently across modules.

Written by the indexing model from the issue text.

Description

3.10 3.11 stdlib topic-typing type-bug
BPO 46373
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-14.09:06:20.374>
labels = ['type-bug', 'library', '3.10', '3.11']
title = 'TypedDict and NamedTuple do not evaluate cross-module ForwardRef in all cases'
updated_at = <Date 2022-01-14.09:06:20.374>
user = 'https://github.com/aha79'

bugs.python.org fields:

activity = <Date 2022-01-14.09:06:20.374>
actor = 'andreash'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2022-01-14.09:06:20.374>
creator = 'andreash'
dependencies = []
files = []
hgrepos = []
issue_num = 46373
keywords = []
message_count = 1.0
messages = ['410547']
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 = 'behavior'
url = 'https://bugs.python.org/issue46373'
versions = ['Python 3.10', 'Python 3.11']

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.