add python-taplo

[bollwyvl]

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.

Notes:

• shouldn't need to exist, but am starting to see (and likely promote) taplo in pyproject.toml#/project.dependencies
  • the upstream wheels only ship a scripts/taplo(.exe) (the compiled binary)
  • but we want to keep pip check working
• this strips out the maturin dependency and all build metadata, relying on @conda-forge/taplo to provide the actual item on $PATH
• it will fail loudly if pyproject.toml changes significantly, but that's good in this case

[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 just wanted to let you know that I linted all conda-recipes in your PR (recipes/python-taplo/recipe.yaml) and found it was in an excellent condition.

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

For recipes/python-taplo/recipe.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • For the run section of 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/13975480111. 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/python-taplo/recipe.yaml) and found it was in an excellent condition.

[bollwyvl]

@conda-forge/help-python ready for review

[bollwyvl]

thanks!

…

On Thu, Mar 20, 2025, 13:17 Filipe ***@***.***> wrote: Merged #29478 <#29478> into main. — Reply to this email directly, view it on GitHub <#29478 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAALCRDDBILDBZ5BQPTQXJD2VMA2VAVCNFSM6AAAAABZOBA2X2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJWHEYTKOBTG4YTCMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>