Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose Python interface for other Rust applications? #3

Closed
kylebarron opened this issue Feb 5, 2024 · 1 comment · Fixed by #4
Closed

Expose Python interface for other Rust applications? #3

kylebarron opened this issue Feb 5, 2024 · 1 comment · Fixed by #4

Comments

@kylebarron
Copy link
Contributor

👋 I'm building a Rust-Python library that depends on object-store. It would be nice to reuse existing Python APIs that are built on object-store, i.e. your crate. From this comment and this comment, I think the primary way to enable this is to split into two crates: an rlib crate that contains everything but the actual #[pymodule] definition and a cdylib crate that is the actual Python module. The former would be able to be depended on by multiple pyo3 libraries, while the latter would be your existing Python package.

I know this is an increase in complexity, but are you interested in a PR for this?

@roeap
Copy link
Owner

roeap commented Feb 5, 2024

Hey @kylebarron - I have been meaning to put some more TLC in this library, as there have been a bunch of updates since last release.

Since the API surface is fairly narrow, I think we can live with a bit more complexity, so yes, quite interested if it makes it more useful :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants