Add marray recipe

[mdhaber]

I (mdhaber) am willing to be listed in the maintainer section.

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 I found some lint.

File-specific lints and/or hints:

• recipes/marray/meta.yaml:
  • lints:
    • Feedstock with the same name exists in conda-forge.

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

Here's what I've got...

For recipes/marray/meta.yaml:

• ❌ There are too few lines. There should be one empty line at the end of the file.

For recipes/marray/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).

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

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

[mdhaber]

@bluescarni it looks like you are the recipe maintainer for marray. We (some SciPy/NumPy/XArray maintainers) are developing a package that adds support for masks (missing data) to any Python Array API Standard compliant array backend, and we have been calling it marray, too. It is currently released on PyPI as such, and we were hoping to release it on conda-forge, too, but it looks like we have a name conflict. Is your project still active? If not, could we use the name in the future?

[lucascolley]

cc @bjoern-andres also