Update scipy to 1.16.0

[jan-janssen]

Summary by CodeRabbit

• Chores
  • Updated the version of the scipy package to 1.16.0 in all environment and configuration files.

[coderabbitai]

Walkthrough

The scipy package version was updated from 1.15.2 to 1.16.0 across multiple environment configuration files, including those for MPICH, OpenMPI, Binder, and the optional dependency group in pyproject.toml. No other dependencies or configurations were modified.

Changes

Files	Change Summary
.ci_support/environment-mpich.yml .ci_support/environment-openmpi.yml binder/environment.yml	Updated scipy version from 1.15.2 to 1.16.0
pyproject.toml	Updated scipy version in ase group to 1.16.0

Estimated code review effort

1 (~2 minutes)

Possibly related PRs

• Bump scipy from 1.14.0 to 1.14.1 #245: Updates scipy version in similar environment files, but to a different version.
• Update mpich to 4.2.3  #259: Changes mpich version and removes scipy from the MPICH environment file, involving the same dependency.

Suggested labels

dependencies

Poem

A hop and a skip, a version anew,
Scipy’s been bumped, the numbers grew.
In every file, the change is clear,
1.16.0 is finally here!
🐇✨
With dependencies fresh, our code will run,
Another review—another job well done!

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.15%. Comparing base (7631d80) to head (43a864b).
Report is 2 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@ ## main #346 +/- ## ======================================= Coverage 81.15% 81.15% ======================================= Files 5 5 Lines 552 552 ======================================= Hits 448 448 Misses 104 104 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

pyproject.toml (1)

40-42: Pin update LGTM – keep an eye on tight version lock.

Exact pinning (==1.16.0) ensures full reproducibility and matches the other env files, so 👍. Just remember this prevents automatic uptake of patch releases; if that becomes a maintenance burden consider a ~=1.16 spec instead.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d10850b and 43a864b.

📒 Files selected for processing (4)

• .ci_support/environment-mpich.yml (1 hunks)
• .ci_support/environment-openmpi.yml (1 hunks)
• binder/environment.yml (1 hunks)
• pyproject.toml (1 hunks)

🔇 Additional comments (3)

binder/environment.yml (1)

10-10: Confirm availability of scipy 1.16.0 on conda-forge for all supported Python versions.

The bump itself looks correct, but because this file is consumed by Binder (potentially on multiple Python minor versions), please double-check that scipy =1.16.0 is already published for every interpreter listed in requires-python (3.9–3.12). A missing build will break the environment solve.

If everything is present, no further changes are needed.

.ci_support/environment-openmpi.yml (1)

11-11: Verify new SciPy build exists for the OpenMPI stack.

Identical note as for Binder: ensure conda-forge/linux-* (and os-x) binaries of scipy 1.16.0 built with OpenBLAS are already available; CI will fail early otherwise.

.ci_support/environment-mpich.yml (1)

11-11: Consistency check passes; please run a quick mamba env create locally.

The version bump is consistent across all env files; a local solve with mamba (or the CI matrix) will confirm there are no hidden conflicts with mpich builds.