manually start PyPy migration

[mattip]

Checklist

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

The dependency resolver bot did not start the pypy3.8/3.9 migration because pyqt is a parent in the graph. But I think pyqt is an optional dependency, not a hard one. The PR works around the problem by manually adding the migration file.

[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.

[mattip]

For some reason CI did not start.

@conda-forge-admin please restart ci

[mattip]

Thanks!

[jakirkham]

Thanks Matti and Ryan! 🙏

[mattip]

This package is now available, but the migration bot doesn't seem to have picked it up. matplotlib is still at the top of the "awaiting parents" group on the pypy3.8 migration. Is there a way to tell the bot that this migration is finished?

[jakirkham]

cc @conda-forge/bot

[jakirkham]

Surfaced the discussion here on Gitter.

[mattip]

Still no movement, migration of the package seems in limbo.

[jakirkham]

Would just raise it in the meeting this week

[chrisburr]

I think it's because pyqt isn't migrated so it's not even considering matplotlib yet. Either that PR should be fixed or we can probably edit the bot metadata directly.

I think this would involve adding a section like:

• https://github.com/regro/cf-graph-countyfair/blob/3f7e9f2e22a8be6b0a9af6462555c2eab3a56f9c/node_attrs/numpy.json#L889-L907

to:

• https://github.com/regro/cf-graph-countyfair/blob/3f7e9f2e22a8be6b0a9af6462555c2eab3a56f9c/node_attrs/matplotlib.json

I'll try to take a look this morning.

[chrisburr]

Actually I found the proper fix that matches how this has been done for pypy37: conda-forge/conda-forge-pinning-feedstock#3326

[mattip]

Great, the migration seems unstuck now.

[jakirkham]

Thanks Chris! 🙏

Maybe we should document this for future reference. Matti, would you be willing to add this to the docs?

[mattip]

the docs

Sure, where in the docs would be appropriate?