Add package multifutures

[brey]

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/multifutures/meta.yaml:
  • lints:
    • Feedstock with the same name exists in conda-forge.
    • The following maintainers have not yet confirmed that they are willing to be listed here: tomsail, pmav99. Please ask them to comment on this PR if they are.

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

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

For recipes/multifutures/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the run 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/12331564646. Examine the logs at this URL for more detail.}

[brey]

@pmav99 & @tomsail please accept the role of maintainer.

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

Here's what I've got...

For recipes/multifutures/meta.yaml:

• ❌ requirements: run: python >= 9999 should not contain a space between relational operator and the version, i.e. python >=9999

For recipes/multifutures/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the run 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/12331592797. 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/multifutures/meta.yaml) and found it was in an excellent condition.

[tomsail]

I am willing to be listed as a maintainer.

[xhochy]

The feedstock already exists: https://github.com/conda-forge/multifutures-feedstock

[brey]

Ping @pmav99