ipython 8.0.0

[bollwyvl]

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [ ] Bumped the build number (if the version is unchanged)
• [x] Reset the build number to 0 (if the version changed)
• [x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [x] Ensured the license file is being packaged.

[conda-forge-linter]

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.

[Carreau]

LGTM,

We may want to have a 7.x branch at some point as I will likely do a few 7.x releases.

Thanks !

[bollwyvl]

Carreau added the automerge label 32 seconds ago

bold play!

7.x branch

done. #157 adds it to the abi_migrations for e.g. py311 or whatever.

[Carreau]

adds it to the abi_migrations for e.g. py311 or whatever.

I have no clue what this is for, but thanks !

[bollwyvl]

what this is for

it's so that the autotick bot knows which branches of the repo should get changes when a package needs to rebuilt for some specific upstream: in our case, we're sensitive to {os, python implementation, python version} but other things might have {numpy}or {llvm} in the mix.

what it won't do is track the upstream branch or anything, so all 7.x PRs will be manual... but so are all of ours at this point. theoretically, if we removed the migrating stuff, we'd get bot PRs back... but it's actually been pretty handy, and the better play might be to dig into the guts of the bot and make it work.

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!