Richard Höchenberger

> For adding to params maybe we'd do it someday but I think we'd want numpy/numpydoc#196 to be resolved to avoid duplication in docstrings and type hints > I've been...

I just wanted to start working on this, adding return type hints to our `mne.io.read_raw_*` functions, but I discovered that most (all?) readers only return a `BaseRaw` child, except for...

> `Raw` is the publicly documented class. In theory we could document `BaseRaw` instead and link there. Or we could document _all_ raw subclasses and (properly) type annotate that we...

> ipython does not have this pb. Wow, you're right! Great, this gives me something to work with.

I've opened a feature request upstream at Pylance: https://github.com/microsoft/pylance-release/issues/346

Just wanted to let you know that this issue still has not been addressed upstream. If you have a minute, it would be great if you could add a 👍...

I took a step forward here since I don't think we'll ever see a fix in the VS Code Python extension / Pylance. The problem is that Pylance and other...

Hello all, thanks for the positive feedback on the type stubs! For those who didn't follow the discussion: I've created "stub files" (`.pyi`) that contain the "expanded" docstrings for all...

Thanks for the feedback and summary, @drammock! I discussed with @cbrnr and I believe we have a solution that we'll be able to integrate into MNE. I'm currently bedridden though...

> Also, I'd argue that we need the stubs package with expanded docstrings not only for releases. After all, developers are going to benefit, and they are working with the...