unpause win-pypy migration

[h-vetinari]

Follows #1668 & #1670, now that numpy has been built, see here.

CC @isuruf @beckermr @mattip

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

Do you understand why the migration status shows matplotlib as a child of pyqt (in the In-PR section)? The recipe only requires pyqt for CPython

[h-vetinari]

I think that's a simple case of the migrator not taking into account selectors. In such cases (barring changes to the migrator, cf. regro/cf-scripts#1331 / regro/cf-scripts#1332), you can simply do a manual migration like conda-forge/numpy-feedstock#238

[mattip]

xref conda-forge/matplotlib-feedstock#298. Once (if?) that goes in, will the migrator then notice and continue from there?

[h-vetinari]

Once (if?) that goes in, will the migrator then notice and continue from there?

No, the migrator only knows its own PRs. But one could then close the pyqt one, and would then continue, I believe.