`taplo` is only a runtime dependency, don't add it as `pyproject.toml` dependency

[sanmai-NL]

Since taplo is only a runtime dependency, don't list it in pyproject.toml. Handle the case where its CLI isn't available gracefully.

Adding taplo as a dependency limits use of this package as dependency to people prepared to compile taplo or on some most common platform for which pre-built binary wheels are available.

[hukkin]

taplo is only a runtime dependency, don't list it in pyproject.toml

That's what the dependency list is for though, they are all runtime dependencies. There's a separate list for build dependencies where taplo definately doesn't belong in.

Adding taplo as a dependency limits use of this package as dependency to people prepared to compile taplo or on some most common platform for which pre-built binary wheels are available

What platform are you using that doesn't have a pre-built wheel? This seems to be taplo's platform matrix for building wheels. If possible, best would be to have your platform included in it, I think.

Having the dependency is convenient as it removes the need to ask people to manually install dependencies, require install extras, or whatever the alternative is. And document all of that.

[elliotweiser]

Normally, I'd agree with you @hukkin because I optimistically hope that all my dependencies are reliably installable by pip. Unfortunately that's not the case with taplo, specifically.

What platform are you using that doesn't have a pre-built wheel?

manylinux + arm64 (example: devcontainer running on Mac with Apple Silicon)

This would be fine if the source distribution of taplo was buildable withpip + setuptools during pip install. It is not.

So the assumption above breaks.

I do agree that expanding taplo's build and release matrix is the right thing to do. However, given the uncertainty of how the taplo project will be maintained, I recommend loosening the coupling on taplo in this project.

A few different methods come to mind:

• Optional dependencies section in pyproject.toml
• Don't install taplo at all. Let the user decide how they will install it separately (e.g. brew, binaries, etc.). If the executable is not detected in the PATH, raise an exception and link them to the official installation page

I will be happy to submit a PR to this effect (and will likely do so), though I'm curious to know if this added context changes your perspective.

UPDATE: I implemented the changes I needed and it satisfied my use-case. Aiming to submit a PR as soon as I get clearance within the next few days or so.

[elliotweiser]

Pull request incoming from my other account.