[SciPy-Dev] New subpackage: scipy.data

Ralf Gommers ralf.gommers at gmail.com
Sun Apr 29 02:41:39 EDT 2018


On Sat, Apr 28, 2018 at 11:21 PM, Robert Kern <robert.kern at gmail.com> wrote:

> On Sat, Apr 28, 2018 at 10:46 PM Ralf Gommers <ralf.gommers at gmail.com>
> wrote:
> >
> > On Mon, Apr 2, 2018 at 11:50 AM, Warren Weckesser <
> warren.weckesser at gmail.com> wrote:
>
> >> (c) We actually *use* the dataset in one of *our* docstrings or
> tutorials.  I don't think our datasets package should become a repository
> of interesting scientific data with no connection to the scipy code.  Its
> purpose should be to enrich our documentation.  (Note that by this
> criterion, the recently added ECG signal would not qualify!)
> >
> > I'd add the criterion that we should *only* use any dataset in the docs.
> Hence there are zero internal imports, and the whole datasets submodule can
> then very simply be stripped for space-constrained usage scenarios. (in
> those cases a separate package would help even)
>
> I believe that one of the motivations for adding the ECG dataset was to
> make some of the scipy.signal unit tests more realistic. Is that something
> you'd like to forbid? On the one hand, if you're strapped for space, you
> probably want to remove the test suites as well. On the other hand, you do
> want to be able to test your stripped installation!
>

Hmm, tough question. Ideally I'd like to say yes, however we do need test
data in some cases. In practice I think one would want to strip the test
suite anyway; scipy/special/tests/data/*.npz is over 1 MB already. So let's
say that importing from within tests is okay.

Ralf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20180428/bafa35fb/attachment-0001.html>


More information about the SciPy-Dev mailing list