ImportError: cannot import name 'aio' from 'grpc.experimental'

[s22chan]

Checklist

• Used a fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• 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.

Fixes #44

See googleapis/python-api-core#41

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

[s22chan]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.

[tswast]

Is this based off of the latest from master? The build appears to be failing in this PR but wasn't after @ocefpaf's edits to #43

[s22chan]

@tswast the build is failing because 1.20.0 should never have been published (conda-forge doesn't have the requisite grpcio version available for any of the google-api-core-grpc calls to work).

The conda recipe is no longer aligned with what's in the setup.py since 1.19.1:
googleapis/python-api-core@4b11422

[tswast]

Gotcha. Looks like grpcio is a bit behind right now. https://github.com/conda-forge/grpcio-feedstock

[tswast]

I tried closing and re-opening to kick off tests now that the grpcio package got an update, but I'm unable to reopen.

[tswast]

the grpcio package got an update

Oh. It's still behind. Only at 1.27.2 currently (conda-forge/grpcio-feedstock#19)

[s22chan]

I think. it's the rerender command, I'm not sure though. In any case, I can't reopen the PR either