ffi: Add Python bindings UniFFI config

[MatMaul]

Those changes allow to build functional Python wheel of the crypto FFI layer using maturin.
Something is still not right for the full SDK FFI, I am looking into it but it should be a change on maturin side.

Currently depends on a change in maturin.

• Public API changes documented in changelogs (optional)

Signed-off-by: Mathieu Velten mathieu@velten.xyz

[Hywan]

Hello and thanks for your contribution.

While I acknowledge it can be useful to support Python, we don't want to support it here as it means we will also be responsible to publish wheels/packages to pypi etc., which we won't.

I'm sorry but we don't want to provide official Python support for the moment.

[MatMaul]

I understand you don't want too much support burden and I am not asking to provide official support or wheels, but can we still work on basic support like this PR ? By adding an explicit disclaimer (no official support, no build, experimental) in the README for example.

FYI I am trying to solve libolm deprecation for the content scanner.

[poljar]

I understand you don't want too much support burden and I am not asking to provide official support or wheels, but can we still work on basic support like this PR ? By adding an explicit disclaimer (no official support, no build, experimental) in the README for example.

FYI I am trying to solve libolm deprecation for the content scanner.

Since our conversation over at element-hq/matrix-content-scanner-python#64, can this be closed?

I would be fine with some of these changes, if they don't hurt the Kotlin/Swift bindings, but including the pyproject.toml file really seems wrong since we don't intend on publishing this to PyPi.

On the other hand, if you don't need this, let's close it.

[MatMaul]

Let's close for now, thanks for the feedback.