Feature or enhancement

I propose that we deprecate the following two ways of creating emptyTypedDicts:

fromtypingimportTypedDictT=TypedDict("T")T2=TypedDict("T2",None)

Pitch

Users currently have four distinct options if they want to create an emptyTypedDict with no fields:

T=TypedDict("T")T2=TypedDict("T2",None)T3=TypedDict("T3", {})classT4(TypedDict): ...

Of these four options, onlyT3 andT4 are supported by type checkers.typing.TypedDict has been around for a while now, so ifT1 andT2 are still unsupported by type checkers, they probably never will be supported.

Deprecating, and eventually removing, the first two ways of constructing empty TypedDicts will allow us to simplify the code at runtime. It will also be less confusing for users. Every way in which the runtime and type checkers differ in behaviour is a potential point of confusion for users; in general, we should work to keep these points of difference to a minimum.

I also don't think these methods of constructing empty TypedDicts are particularly common.

Previous discussion

For very similar reasons, we previously deprecated and removed the keyword-argument syntax for creating TypedDicts. This was deprecated in 3.11, and removed in 3.13:

• Deprecate keyword args syntax for TypedDict definition #90224
• Remove kwargs-based TypedDict creation #104786

In retrospect, we should really have deprecated these ways of creating empty TypedDicts at the same time. But there's no way of changing that now.

Linked PRs

• gh-105570: Deprecate unusual ways of creating empty TypedDicts #105780