Add recipe for meson-python

[awvwgk]

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

[conda-forge-linter]

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/meson-python) and found some lint.

Here's what I've got...

For recipes/meson-python:

• The top level meta keys are in an unexpected order. Expecting ['package', 'source', 'build', 'requirements', 'test', 'about', 'extra'].

[conda-forge-linter]

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/meson-python) and found it was in an excellent condition.

[awvwgk]

@conda-forge/help-python This recipe is ready for review. While I would prefer noarch: python, it seems more important to support all Python versions to not limit other Python packages planning to use this one as build system (like SciPy).

[rgommers]

Thanks for working on this @awvwgk!

The patch here looks wrong to me. If there's something to fix, let's do it upstream. But the reason for changing ninja requirements here is not correct either way: when one uses build isolation in a Python venv, a ninja installed by conda-forge cannot be used.

This package should be noarch. The pip check failure may be due to incorrect metadata in pyproject.toml; if needed a patch can be carried for that until it's fixed in the next meson-python release.

[awvwgk]

Seems like this is ready for review again, now as noarch: python.

[rgommers]

LGTM overall now, thanks @awvwgk

[rgommers]

LGTM, thanks!

[rgommers]

@conda-forge/staged-recipes can this be merged?