Adding icepyx package

[lsetiawan]

Overview

This PR adds icepyx to conda-forge.

Pinging @JessicaS11 so that you're aware. Let me know if there are changes that need to be made in terms of dependencies.

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

[weiji14]

Got hit with a setuptools_scm v0.0.0 version string related issue today at conda-forge/pygmt-feedstock#15, thought I'd save icepyx from some drama. See also a related PR at conda-forge/pint-feedstock#34.

[weiji14]

Let's see if icepyx v0.3.3 from PyPI works

[weiji14]

Hmm, that Windows build failure is interesting, probably because of this line that's setting the environment variable in a UNIX-only way?

staged-recipes/recipes/icepyx/meta.yaml

Line 16 in be41653

script: SETUPTOOLS_SCM_PRETEND_VERSION={{ version }} {{ PYTHON }} -m pip install . -vv

I thought that no-arch packages https://conda-forge.org/docs/maintainer/knowledge_base.html#noarch-python are only built on Linux, so not sure what we should do here :/

[lsetiawan]

@conda-forge/staged-recipes This is ready for review. Thank you so much for your time!

[ocefpaf]

If it is noarch you don't need this. It will failed on the CIs here but there will be no Windows CI in the feedstock. It won't hurt either, but it will never be used.

[lsetiawan]

Okay. So we did do that but the windows CI failed. What you are saying is that would have been fine?

[ocefpaf]

Yep. What @weiji14 said in #13866 (comment) is correct.

There are rare cases of things that pretend to be noarch, passes on Linux, and they we find out that should've been tested on Windows. But if you ever find on of those cases the Windows users will let you know and you'll remove the noarch in the feedstock later.

[lsetiawan]

Cool. Thanks for that explanation 😄