add easysnowdata package

[egagli]

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.

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[conda-forge-admin]

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/easysnowdata/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/easysnowdata/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12729746208. Examine the logs at this URL for more detail.}

[synapticarbors]

Please look at the docs for noarch: python recipes:
https://conda-forge.org/docs/maintainer/knowledge_base/#noarch-python

specifically the use of {{ python_min }}. This will fix up your linting errors.

[synapticarbors]

Trying changing bs4 to beautifulsoup4. I'm not sure, but I'm hoping this fixes the pip check errors.

[egagli]

I think that worked, thank you!

[egagli]

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

[conda-forge-admin]

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/easysnowdata/meta.yaml) and found it was in an excellent condition.

[synapticarbors]

So it looks like it's failing because the python_min is 3.9, but the package uses syntax like:

def get_forest_cover_fraction(bbox_input: gpd.GeoDataFrame | tuple | shapely.geometry.base.BaseGeometry | None = None, mask_nodata: bool = False,

where the pipe | for union is only supported in python 3.10 and higher. This means that the upstream python_requires in the pyproject.toml is wrong and you you would need to add {% set python_min = "3.10" %} at the top of the recipe below the version jinja.

[egagli]

@synapticarbors Thank you so much for your help! I think we're all set now?