[Request]: provide custom backend to use plugin without invoking poetry directly.

[kclaes]

We're using tooling that invokes the build of our Python project using PEP 517: python -m build --sdist
By default, this uses poetry-core and as such, does not load plugins.

We've noticed in other projects, like https://github.com/mtkennerly/poetry-dynamic-versioning, a custom build-backend to put into pyproject.toml that wraps poetry-core and executes the functionality of the plugin.

Would it be possible to provide something similar for this plugin?

Or, if there's another way to do this, I'd love to hear about it.

Currently using this config in pyproject.toml:

[build-system]
requires = ["poetry-core", "poetry-plugin-mono-repo-deps"]
build-backend = "poetry.core.masonry.api"

[gerbenoostra]

That's actually a nice idea, but it also plugs in at a different point in Poetry's flow. One uncertainty is how two such wrappers would be able to coexist in one build setup.

I'll also take a look at the way poetry-dynamic-versioning patches the versions, perhaps it provides an interesting alternative.