Include explicit Python dependencies

[cofinoa]

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.

[conda-forge-webservices]

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

I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

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

[mfansler]

This seems misguided. R packages that need to run Python should use reticulate to establish dedicated (isolated) environments for the Python software they need. It almost never makes sense to have coinstallation of R and Python in the same environment. I would urge the changes here be reconsidered.

[cofinoa]

@mfansler you are probably right.

IMO, this needs to be considered at R package level, where packages should be installed/deployed on demand.

This build is a hotfix for missing python, and its dependencies, needed by the R original package and raised (see
SantanderMetGroup/climate4R#61) which just assume that python and its dependencies are already available.

A dedicated environment (i.e. r-reticulate) is being used by default, but it's not required (see Python Version Configuration)