Allow multiple Python versions in recipe

[peanutfun]

Bump build number.

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.

[conda-forge-webservices]

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.

[peanutfun]

@conda-forge-admin, please rerender

[conda-forge-webservices]

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:

• noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

[conda-forge-webservices]

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.

[peanutfun]

@emanuel-schmid I am not sure if this does the trick, but we can give it a try and see afterwards. If it does not work, I will ask a question in the conda-forge Q&A forum. I tried using conda_build_config.yaml, but this has no effect, because a Python package is technically not "built" (note that there is no "build" section in the meta.yaml either) edit: That's wrong, I just don't know if it had any effect 🤷

I just noticed that we did not release v4.1.1 yet. So, if we introduce an issue here, we can fix it right away afterwards and release v4.1.1 😉