add-marvin

[raybellwaves]

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/marvin/meta.yaml) and found some lint.

Here's what I've got...

For recipes/marvin/meta.yaml:

• ❌ The summary item is expected in the about section.
• ❌ Non noarch packages should have python requirement without any version constraints.
• ❌ Non noarch packages should have python requirement without any version constraints.

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

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

For recipes/marvin/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
  • For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
  • 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).

[raybellwaves]

got partialjson >=0.0.5 does not exist (perhaps a typo or a missing channel)..

Working on that here: #28255

[synapticarbors]

I think you need to use the python_min convention mentioned in https://conda-forge.org/docs/maintainer/knowledge_base/#noarch-python for new noarch packages. I tend to use the jinja variable {% set python_min = "3.9" %} explicitly at the top of the recipe.