Allowed for newer python

[pariterre]

Checklist

• [ ] Used a 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 code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [ ] Ensured the license file is being packaged.

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

[pariterre]

@conda-forge-admin, please rerender

[pariterre]

@pstjohn Sorry again, conda-forge automatically assign the review!

[pariterre]

@conda-forge-admin, please rerender

[github-actions[bot]]

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

[pariterre]

@conda-forge/staged-recipes Hi there! I am desperately trying to compile for Python3.8, but I can't find what is blocking the 3.8 from being testes by feedstock. Do you have any clue?

[pariterre]

@conda-forge-admin, please rerender

[github-actions[bot]]

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

[beckermr]

Python 38 is done by a migrator and so some of your deps probs don't have it yet.

cc @conda-forge/bot

[pariterre]

@beckermr Thanks for your answer! Is that mean that there is nothing I can do right now, meaning that I should accept the PR as is and someday it will work?

[beckermr]

There is a way to hack it in, but i'd just merge for now.

cc @conda-forge/core we should consider moving python 38 into the global pinnings.