Manual pypy3.7 migration build

[h-vetinari]

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.

I was wondering why conda-forge/pandas-feedstock#106 had been opened by the migrator already, and couldn't find numpy listed anywhere in the migration page. Trying a manual build, but happy to close if this should be done differently.

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

[h-vetinari]

Depends (at least) on conda-forge/pytest-feedstock#132

[hmaarrfk]

Seems like there is a missing dependency on aarch.

[h-vetinari]

Nope, that's just because drone didn't pick up the restart.

[isuruf]

@conda-forge/bot, was there any code added to the bot to skip any packages in the migration yaml itself? Looks like the bot is skipping numpy for this migration

[github-actions]

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

I considered the following status checks when analyzing this PR:

• linter: passed
• drone: passed
• travis: passed
• azure: passed

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

[h-vetinari]

There's a ppc build that failed on master - could some one restart it?