Manual migration for PyPy windows

[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 migrations dependency resolver ignored the selector on pyqt, and is waiting for pyqt (which will not work on PyPy), so try this manually.

I did not update the build number since this is a migration.

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

Hit a build error in _c_internal_utils.c in return PyErr_SetFromWindowsErr(hr);

src/_c_internal_utils.c(71): error C2440: 'return': cannot convert from 'void' to 'PyObject *'

PyPy doesnt' do this right. Patch needed.

[conda-forge-linter]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [14]

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

It seems some other package is not available yet? I am not sure which one.

[mattip]

Close/reopen to restart CI

[mattip]

CI is passing.

[mattip]

Thanks!

[mattip]

This is still marked on the PyPy windows migration as "waiting for parents" @isuruf is that blocking anything, and if so is there a way around it?

[isuruf]

cc @conda-forge/bot

[mattip]

I still see this as "waiting for parents" on the PyPy windows migration, even though this PR was merged. Is there a way around that?

[mattip]

Hmm. The migration bot still does not recognize matplotlib as updated.

[dopplershift]

@mattip Just to be clear, this is last year's issue. Probably meant #322.

[mattip]

Thanks for the correction, yes I meant #322. The PRs were similarly named, sorry for the confusion. In any case any ideas how to convince the migration bot that this package is available for pypy3.8/3.9?

[jakirkham]

xref: #322 (comment)