Inconsistent type inference with `type(None)`

[smackesey]

Bug Report

TYPE_NONE = type(None)
reveal_type(type(None))  # => `Type[None]`
reveal_type(TYPE_NONE)  # => `builtins.object`

Expected Behavior

The two reveal_type calls above should print the same thing (Type[None])

Your Environment

• Mypy version used: 0.942
• Python version used: 3.10.4
• Operating system and version: macOS 12.3.1

[Zeckie]

Is that different from this (ie. reveal_type giving a narrow type for something it recognises)?

one = 1
reveal_type(1)  # note: Revealed type is 'Literal[1]?'
reveal_type(one)  # note: Revealed type is 'builtins.int'

[smackesey]

Not sure-- probably share a similar root but IMO the example I posted is even less intuitive (one is a Type, the other is builtins.object) because this pattern does not occur when you use a different type (like int in place of type(None)).

[brianschubert]

As of #16315 (released with mypy v1.9.0), mypy infers type[None] for both cases.