search

conda-forge / pymc3-feedstock

A conda-smithy repository for pymc3.
BSD 3-Clause "New" or "Revised" License
5 stars 17 forks source link

Rebuild for python311 #80

Open regro-cf-autotick-bot opened 1 year ago

regro-cf-autotick-bot commented 1 year ago

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

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.

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. 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/3603202517, please use this URL for debugging.

conda-forge-linter commented 1 year 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.

maresb commented 1 year ago

Unless someone has a good reason, I think we want to not support this, right?

twiecki commented 1 year ago

Python 3.11? Why not?

maresb commented 1 year ago

Because pymc3 is old news now, no? Is there a use case for upgrading Python to 3.11 without upgrading PyMC to 4?

michaelosthege commented 1 year ago

oh right, this is the v3 feedstock!

ain't nobody got time for that

maresb commented 1 year ago

I'm pretty sure it makes no difference in this case, but in general we shouldn't close these migrations without seeing them through:

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.