Add recipe for ZodiPy

[MetinSa]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[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 (recipes/zodipy) and found some lint.

Here's what I've got...

For recipes/zodipy:

• The home item is expected in the about section.

[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 (recipes/zodipy) and found it was in an excellent condition.

[MetinSa]

This PR is to make ZodiPy conform to the pyOpenSci packaging guidelines (see pyOpenSci/software-submission#161).

[MetinSa]

@conda-forge/help-python, ready for review!

[lpsinger]

The build is failing due to conda-forge/healpy-feedstock#64.

[dhomeier]

Thanks for the pointer; perhaps @mwcraig can advise?
Another issue is that healpy is not available on Windows, so other packages depending on it have disabled the Windows build, but I am not sure what's the best way to go about this.
Seems other packages depending on healpy are just skipping the build or ignoring failures. ZodiPy is a bit different in that it has a minimum version requirement, but in my macOS miniforge installation conda/mamba indeed identify the healpy version correctly; it's just pip reporting it as 0.0.0.

[MetinSa]

ZodiPy is a bit different in that it has a minimum version requirement, but in my macOS miniforge installation conda/mamba indeed identify the healpy version correctly; it's just pip reporting it as 0.0.0.

I generated the meta.yaml file using grayskull and saw that it set both lower and upper bounds for many of the dependencies. I was not sure if this was required or not by conda-forge, so I didnt change it. I did not set a minimum requirement for healpy in pyproject.toml so i could try to relax this in the meta.yaml file and try again if you think that could help?

[lpsinger]

ZodiPy is a bit different in that it has a minimum version requirement, but in my macOS miniforge installation conda/mamba indeed identify the healpy version correctly; it's just pip reporting it as 0.0.0.

I generated the meta.yaml file using grayskull and saw that it set both lower and upper bounds for many of the dependencies. I was not sure if this was required or not by conda-forge, so I didnt change it. I did not set a minimum requirement for healpy in pyproject.toml so i could try to relax this in the meta.yaml file and try again if you think that could help?

One moment. I am looking into the issue with healpy. It would be better if we could fix that bug.

[lpsinger]

One moment. I am looking into the issue with healpy. It would be better if we could fix that bug.

conda-forge/healpy-feedstock#65 should fix it.

[lpsinger]

Fixed. Please try again.

[MetinSa]

The non-windows builds work now, thanks! I am going to see if it still builds with a more relaxed dependency configuration matching thepyproject.toml.