Warren Weckesser

Note that I don't mean literally "all at once" as in one massive pull request. I mean making steady progress so that the task is complete for 1.10.

> So IMO we should not set ourselves to finish this specifically for the next release. I think this is not the best decision, and it does not reflect the...

Anyway, it probably makes sense to have just one github issue for this. I could either: * Close gh-13049, and use this issue as the tracker for updating the docstrings...

Thanks, @ak04p. In case you are planning to continue working on this, note that in https://github.com/scipy/scipy/pull/16831 I have updated the docstrings in the file `scipy/special/_add_newdocs.py`, which will take care of...

@BassCoder2808, yes, please do!

@dna-witch, we don't assign tasks, so you can go ahead and work on it. The pull request https://github.com/scipy/scipy/pull/17110 will take care of the examples in the `sparse` subpackage. Other than...

@dna-witch, in case you have started working on this, take note of https://github.com/scipy/scipy/pull/17115. That pull request fixes most of the docstrings.

Just to be clear: https://github.com/scipy/scipy/pull/17115 is almost done, and after that is merged, there won't be a lot of examples left to fix.

@BassCoder2808's pull request updated 210 docstrings (:rocket:!), leaving just 14 to go--at least according to the script used above.

FYI: `scipy.special.sinc` is an alias for `numpy.sinc`, so we can ignore that docstring. It would be nice to deprecate and remove `sinc` from the `scipy.special` namespace, but that's a separate...