TYP: libinterval
This one is pretty ugly.

> This one is pretty ugly.

is something awry with mypy or do you know what changes here cause issues with the doc decorator.
 > is something awry with mypy or do you know what changes here cause issues with the doc decorator.

no idea whats making mypy complain > maybe break off the io changes for now

IIRC i did only what was necessary to get mypy to stop complaining about interval.pyi > we can't merge this with all these error: Cannot determine type of ignores that have appeared. not sure what else to suggest.

IIUC mypy's complaint is bc e.g. `Index.memory_usage` is decorated with `@doc(IndexOpsMixin._memory_usage)`.  doc is annotated with `-> Callable[[F], F]` which i would expect would prevent this problem @simonjayhawkins i _think_ the reason why so many new mypy complaints are popping up is because `Scalar` no longer resolves to Any.  will try to chip away at these > this is a lot of change, not sure if easier to do in pieces

Haven't found a good way to do this.  bc this is the last thing that mypy doesnt recognize in pd._typing.Scalar, it means a bunch of things that currently resolve to Any are now recognized.  I'll keep trying this periodically, but for the time being this is on the backburner. can pandas/_libs/tslibs/nattype.pyi or pandas/_libs/interval.pyi be added in seperate PRs. 

also it is possible to partially type a stub so that could be get some of this in. 

https://github.com/python/typeshed/blob/master/CONTRIBUTING.md#incomplete-stubs Mothballing to clear the queue, as there is no clear path forward here.