ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

The INLINE_TYPEDDICT bitflag was added "just in case". I'll remove it if it is not desired.

The INLINE_TYPEDDICT bitflag was added "just in case". I'll remove it if it is not desired.

Yeah, we should remove it if it's not being used currently.

I'll also make a general recommendation to use typed_dict instead of typeddict as I'd consider them two separate words.

Apart from this, I'm not exactly sure what the scope of this should be as the PEP is still in draft so we don't know where all we need to change this. What about when the slice element is not a dictionary like the one in your test case? I don't see it being supported in the PEP yet. Should we only limit it to the following syntax (https://github.com/Viicos/peps/blob/inlined-typed-dictionaries/peps/pep-0764.rst#typing-specification-changes)?

<TypedDict> '[' '{' (string: ':' annotation_expression ',')* '}' ']'

@dhruvmanila When the expression is not a dictionary literal, TypedDict[expr] is invalid as a type expression. In this case, I think expr should be visited as a normal (non-type) expression, which is already the case with this PR.

This PR could be considered provisional support for the PEP. Pyright (and Basedpyright) already did so; parity by other tools could help the PEP gain wider recognition.