Neil Girdhar

After testing this a lot with my code, I think MyPy is [still not ready ](https://github.com/python/mypy/issues?q=is%3Aissue+is%3Aopen+paramspec+label%3Atopic-paramspec)to check code with complex `ParamSpec` usage (although Pyright is). If we check something like...

@JesseFarebro My mistake, I didn't find that when I searched! MyPy has progressed since then, but maybe still not enough. @jakevdp Yes, fair enough. `ParamSpec` seems to work for more...

Great news: Thanks to the recently merged https://github.com/python/mypy/pull/15837, it appears that the main MyPy error with this pull request may have been solved: https://github.com/python/mypy/issues/12169. Also, many of the MyPy errors...

@jakevdp Done. FYI the MyPy pull I linked is merged, but it's not in any released MyPy yet.

@jakevdp MyPy 1.6 is out today, and it may now [support](https://mypy-lang.blogspot.com/2023/10/mypy-16-released.html) using `ParamSpec` as in this pull request. (See the section on ParamSpec improvements.) Is there a process or plan...

Okay, I've rebased this to take advantage of the new MyPy version

Just FYI if you want to get rid of the `typing_extensions` dependency, one option would be to follow [SPEC 0](https://scientific-python.org/specs/spec-0000/), and drop Python 3.9 (since you already support Python 3.12)....

> sometime after April 2024, following NEP 29 (see Fair enough, but isn't NEP 29 now superseded by SPEC 0?

@jakevdp Yes, I'm really looking forward to something like this making it in. I'll need to look at it tomorrow since I have plans tonight. Were you able to update...

Running MyPy 1.6.1, I'm still getting a lot of bad errors: ``` jax/experimental/sparse/linalg.py:102: error: Argument 2 to "__call__" of "Wrapped" has incompatible type "Array"; expected "P.args" [arg-type] jax/experimental/sparse/linalg.py:102: error: Argument...