Repository navigation
Widen NumPy and SciPy compatibility bounds - #410
Merged
Merged
Conversation
Allow NumPy 2.5.4 and SciPy 1.18.1 without raising minimum versions. Keep requirements synchronized and schedule grouped scientific range updates. Assisted-by: GPT-6.1 Sol
Remove the proposed pip automation after verifying that Dependabot can select an older Python interpreter from the supported range and miss newer scientific releases. Keep this PR focused on the requested compatibility bounds. Assisted-by: GPT-6.1 Sol
PierreRaybaut
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
<2.5to<2.6, admitting the latest stable 2.5.4.<1.17to<1.19, admitting the latest stable 1.18.1.pyproject.tomlandrequirements.txt; preserve all minimum versions and Python 3.9 support.Validation
git diff --checkpassed. The existing PR CI is responsible for runtime compatibility qualification; Python 3.9 intentionally resolves older compatible scientific releases.Automation evaluation
The initially proposed Dependabot pip configuration was removed after inspecting its current Python interpreter selection: with the project's broad
requires-pythonrange, the updater can select an older supported interpreter and filter out the recent scientific releases this process is intended to qualify. Per maintainer decision, this PR therefore contains only the compatibility-bound updates, rather than claiming that native Dependabot fully implements the upper-bound policy.DataLab Web's existing npm Dependabot automation is unaffected; its next scheduled run was preferred to manual duplicate PRs.
All work was performed in fresh isolated clones, without modifying existing developer checkouts or installed Python environments.
Coordination
Companion: DataLab-Platform/Sigima#76. Both branches are named
maintenance/scientific-dependency-bounds, so the existing development CI can install the widened Sigima revision. Merge the Sigima PR first. SigimaX has no independent scientific upper bounds and needs no manifest change.The datalab-capsule bound already admits its latest 0.1.0 release. The release-specific PyInstaller pin is intentionally unchanged.