There are a number options that I can see:

1. Go with current protocol and create an EUPS package containing scipy
2. Hope that RFC-50 can be adopted.
3. Make scipy an external dependency as for numpy and matplotlib and make a package that simply checks scipy is available. This option is almost what we have now without the checking.

The first and third options would require scipy to be listed in other table files. Option 3 is by far the easiest to implement.

I'd say we go with option 3. Option 1 is too much overhead and we can't wait for option 2.

Created scipy package and added it to lsstsw/etc/repos.yaml .

Hi Tim,
Would you mind reviewing the scipy package?
I also added it to repos.yaml in lsstsw.
Thanks.

Looks good although I don't think the .cfg file is needed. Also, I'd like the table files of other packages to be fixed as soon as possible so that we have an idea of what is silently depending on scipy. From what I can see this is afw, ip_diffim, meas_modelfit, mops_daymops, pipe_tasks, shapelet and sims_photUtils. I realise you may not want to do that on this ticket but I really do want these dependencies to be fixed sooner rather than later. Many of these are setupOptional that we should consider making mandatory. Some will be setupRequired.

OK, I'll make a new ticket.
DM-5658.

Merged. Thanks for your help, Tim.