conda-forge / scipy-feedstock

A conda-smithy repository for scipy.
BSD 3-Clause "New" or "Revised" License
6 stars 36 forks source link

Rebuild for python310 #194

Closed regro-cf-autotick-bot closed 2 years ago

regro-cf-autotick-bot commented 2 years ago

This PR has been triggered in an effort to update python310.

Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

This package has the following downstream children: cvxpy lal And potentially more.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable. Finally, feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/1424283792, please use this URL for debugging

conda-forge-linter commented 2 years ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

h-vetinari commented 2 years ago

I was thinking of finishing #193 first and then rebasing this one. Unfortunately there's a pypy-hang on aarch (though we could merge #193 regardless and fix it in this PR)

h-vetinari commented 2 years ago

I'll take care of this after #195

h-vetinari commented 2 years ago

@chrisburr, can we please prioritize #195 before merging this?

h-vetinari commented 2 years ago

This will inter alia also solve the error

ERROR: Package 'scipy' requires a different Python: 3.10.0 not in '<3.10,>=3.7'

here, because 1.7.2 is (declared) compatible with python 3.10

chrisburr commented 2 years ago

here, because 1.7.2 is (declared) compatible with python 3.10

Ah right, I suggest merging this into the update branch so it's closed automatically when that PR is moved.

h-vetinari commented 2 years ago

Ah right, I suggest merging this into the update branch so it's closed automatically when that PR is moved.

I'm planning to rebase this branch as soon as #195 is in (the bot won't restart it since there's already a non-bot commit)

h-vetinari commented 2 years ago

OK, the osx+pypy failure is not relevant, because it was already built on master. Merging.