-
-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #38 from regro-cf-autotick-bot/rebuild-numpy2-0-1_…
…h3559cf Rebuild for numpy 2.0 - This migrates `main`. For now an `old-numpy` branch is used to also keep building against 1.x; otherwise versions before 1.25 (which is well above Euphonic's minimum-supported numpy) will break. - Once we can bump the minimum requirement to 1.25 we can drop the old branch and build everything against 2.x
- Loading branch information
Showing
22 changed files
with
139 additions
and
91 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
__migrator: | ||
build_number: 1 | ||
kind: version | ||
commit_message: | | ||
Rebuild for numpy 2.0 | ||
TL;DR: The way we build against numpy has changed as of numpy 2.0. This bot | ||
PR has updated the recipe to account for the changes (see below for details). | ||
The biggest change is that we no longer need to use the oldest available numpy | ||
version at build time in order to support old numpy version at runtime - numpy | ||
will by default use a compatible ABI for the oldest still-supported numpy versions. | ||
Additionally, we no longer need to use `{{ pin_compatible("numpy") }}` as a | ||
run requirement - this has been handled for more than two years now by a | ||
run-export on the numpy package itself. The migrator will therefore remove | ||
any occurrences of this. | ||
However, by default, building against numpy 2.0 will assume that the package | ||
is compatible with numpy 2.0, which is not necessarily the case. You should | ||
check that the upstream package explicitly supports numpy 2.0, otherwise you | ||
need to add a `- numpy <2.0dev0` run requirement until that happens (check numpy | ||
issue 26191 for an overview of the most important packages). | ||
### To-Dos: | ||
* [ ] Match run-requirements for numpy (i.e. check upstream `pyproject.toml` or however the project specifies numpy compatibility) | ||
* If upstream is not yet compatible with numpy 2.0, add `numpy <2.0dev0` upper bound under `run:`. | ||
* If upstream is already compatible with numpy 2.0, nothing else should be necessary in most cases. | ||
* If upstream requires a minimum numpy version newer than 1.19, you can add `numpy >=x.y` under `run:`. | ||
* [ ] Remove any remaining occurrences of `{{ pin_compatible("numpy") }}` that the bot may have missed. | ||
PS. If the build does not compile anymore, this is almost certainly a sign that | ||
the upstream project is not yet ready for numpy 2.0; do not close this PR until | ||
a version compatible with numpy 2.0 has been released upstream and on this | ||
feedstock (in the meantime, you can keep the bot from reopening this PR in | ||
case of git conflicts by marking it as a draft). | ||
migration_number: 1 | ||
|
||
# needs to match length of zip {python, python_impl, numpy} | ||
# as it is in global CBC in order to override it | ||
numpy: | ||
- 1.22 # no py38 support for numpy 2.0 | ||
- 2.0 | ||
- 2.0 | ||
- 2.0 | ||
- 2.0 | ||
migrator_ts: 1713572489.295986 |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.