Test nightly dependencies when possible in CI ?

[Carreau]

Problem Description

in #36975 IPython 8.19 broke sage, and I did a 8.20 release.
It would be great to test pre-release of dependencies to possible warn me ahead of time.

Proposed Solution

A number of nightly wheel are available here:

https://anaconda.org/scientific-python-nightly-wheels/repo (see Spec 4) using --pre --upgrade --extra-index-url https://pypi.anaconda.org/scientific-python-nightly-wheels/simple in the right place should be enough.

I guess weekly cron that open an issue on failure would be enough.

Alternatives Considered

Do nothing, or have upstream test this repo.

Additional Information

I guess it might also catch early issue in SciPy/Numpy...

It is of course an extra burden as nightly is more likely to fail, and maintainer need to decide if it's true failures.

Is there an existing issue for this?

• I have searched the existing issues for a bug report that matches the one I want to file, without success.

[mkoeppe]

In the direction of the alternative "have upstream test this repo":

• We have a reusable workflow for that - see Meta-ticket: CI workflows for upstream projects using Sage reusable workflows #33338

[tobiasdiez]

What about having one central place (scientific ecosystem ci), that runs the current branches of registered projects against the latest versions of their dependencies (or against a certain PR). Something similar to https://github.com/vitejs/vite-ecosystem-ci.

[Carreau]

IMHO a central place to test all does not work well as each project need to be tested slightly differently.

In addition if you run the main branches, then they need to be built, which is always a bit different for each project.

Then when there is a failure, one need to decide who is responsible for investigating, and in which project the failure lies.

I don't think the scientifc Python ecosystem is standardized enough yet for that.