Add PyCifStar to conda-forge

[MridulS]

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 wanted to let you know that I linted all conda-recipes in your PR (recipes/pycifstar/recipe.yaml) and found some lint.

Here's what I've got...

For recipes/pycifstar/recipe.yaml:

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

For recipes/pycifstar/recipe.yaml:

• noarch: python recipes should almost always follow the syntax in our documentation. For the host section of the recipe, you should almost always use python ${{ python_min }} for the python entry. For the run section of the recipe, you should almost always use python >=${{ python_min }} for the python entry. For the test.requires section of the recipe, you should almost always use python ${{ python_min }} for the python entry. You may need to override the python_min variable in the conda_build_config.yaml/variants.yaml if the package requires a newer Python version than the currently supported minimum version on conda-forge.

[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/pycifstar/recipe.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...

For recipes/pycifstar/recipe.yaml:

• noarch: python recipes should almost always follow the syntax in our documentation. For the host section of the recipe, you should almost always use python ${{ python_min }} for the python entry. For the run section of the recipe, you should almost always use python >=${{ python_min }} for the python entry. For the test.requires section of the recipe, you should almost always use python ${{ python_min }} for the python entry. You may need to override the python_min variable in the conda_build_config.yaml/variants.yaml if the package requires a newer Python version than the currently supported minimum version on conda-forge.

[MridulS]

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

Looks like rattler-build doesn't fully support https://github.com/conda-forge/cfep/blob/main/cfep-25.md as there isn't a way to add a lower pin for tests.python in the v1 recipe format. Should I just move to the old recipe format to make the linter happy?

[beckermr]

@conda-forge-admin relint

[MridulS]

@conda-forge-admin relint