For an existing library, what is the best (or at least good) way to structure the project when creating Python bindings via pyo3 / maturin ?
So far I figure I can either just annotate all the structs and impls with #[pyclass] and #[pymethods] directly in the original library along with a #[pymodule] fn, but this changes the return types and litters the original code with the additional attribute annotations.
The other option I can see is to basically copy + paste the library into a new lib with the appropriate Cargo.toml and pyproject.toml, and annotate all the desired structs/impls etc there instead. The benefit of this is you retain the original library as it was, but the downside is that for every implementation in the original, it requires doing the same thing in the secondary pyo3 project which is a tedious task.
The crates polars and tokenizers both seem to do the latter, which I would prefer since I want to keep the original library without the additional attributes everywhere.
Is there a smart way to accomplish this, such as automate it ?