A simple library to allow for easy use of python from rust.

Luke

Last update: Jun 20, 2022

Related tags

Foreign Function Interface rustpy

Overview

Rustpy

A simple library to allow for easy use of python from rust.

Status

Currently this library has not received much love (pull requests welcome for any interested) and does not build with rust 1.0.

For another library that also strives to bridge the gap between python and rust and might be a little more up to day see:

https://github.com/dgrunwald/rust-python27-sys

https://github.com/dgrunwald/rust-cpython

How to Use

This library is meant to be middle ware for users wanting to use python libraries from rust. It allows users to quickly use existing tools and get working on interesting things fast!

See pysmtplib.rs for an example of how to bind enough smtplib to send emails.

For more documentation, run rustdoc src/rustpy.rs and look at doc/rustpy/index.html. Pull requests are welcome!

(untyped_res).unwrap(); assert_eq!(result, 12f32); }">

extern crate rustpy;
use rustpy::{ToPyType, FromPyType, PyState};

fn main() {
  let py = PyState::new();
  let module = py.get_module("math").unwrap();
  let func = module.get_func("sqrt").unwrap();
  let args = (144f32, ).to_py_object(&py).unwrap();
  let untyped_res = func.call(&args).unwrap();
  let result = py.from_py_object::<f32>(untyped_res).unwrap();
  assert_eq!(result, 12f32);
}

Important note: Only create one instance of PyState at a time. On construction, it grabs a global lock to prevent more than one thread from interacting with the interpreter thus making it very easy to deadlock.

Comments

Just my rust setup or something incompatible with latest nightly?

src/rustpy.rs:38:1: 38:19 error: can't find crate for `sync`
src/rustpy.rs:38 extern crate sync;
                 ^~~~~~~~~~~~~~~~~~
error: aborting due to previous error
Could not compile `rustpy`.

opened by geekpete 5

fail -> panic

Sorry I broke your code with rust-lang/rust#17894 ! Here's a fix :heart:

(this is a semi-automatic PR, so sorry if it's not perfect. Let me know and I'll fix any problems.)

opened by steveklabnik 3
error: found possibly newer version of crate `std` which `rustpy` depends on

Hi,

Trying to build the example I get this error: /home/v/ue/rust/v_rustpy1/src/main.rs:1:1: 1:21 error: found possibly newer version of crate std which rustpy depends on

I use the rust-nightly ppa on ubuntu 14.10 and the newest cargo. Thanks

Compiling v_rustpy1 v0.0.1 (file:///home/v/ue/rust/v_rustpy1) /home/v/ue/rust/v_rustpy1/src/main.rs:1:1: 1:21 error: found possibly newer version of crate std which rustpy depends on /home/v/ue/rust/v_rustpy1/src/main.rs:1 extern crate rustpy; ^~~~~~~~~~~~~~~~~~~~ /home/v/ue/rust/v_rustpy1/src/main.rs:1:1: 1:21 note: perhaps this crate needs to be recompiled? /home/v/ue/rust/v_rustpy1/src/main.rs:1 extern crate rustpy; ^~~~~~~~~~~~~~~~~~~~ /home/v/ue/rust/v_rustpy1/src/main.rs:1:21: 1:21 note: crate std path #1: /usr/lib/rust/rust-nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib/libstd-4e7c5e5c.rlib /home/v/ue/rust/v_rustpy1/src/main.rs:1:21: 1:21 note: crate std path #2: /usr/lib/rust/rust-nightly/lib/rustlib/x86_64-unknown-linux-gnu/lib/libstd-4e7c5e5c.so /home/v/ue/rust/v_rustpy1/src/main.rs:1:21: 1:21 note: crate rustpy path #1: /home/v/ue/rust/v_rustpy1/target/deps/librustpy-2037a4f507dfdb30.rlib error: aborting due to previous error Could not compile v_rustpy1.

To learn more, run the command again with --verbose. [Finished in 0.3s with exit code 101] [cmd: ['cargo', 'run']] [dir: /home/v/ue/rust/v_rustpy1/src] [path: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games]

opened by v217 2
how to get around global lock

hey - I have a situation where I need to run some Python code from Rust but I will have many Python processes running simultaneously. I am advanced at Python but a beginner in Rust, so I thought I would reach out regarding how to get around the global lock in this library. Would I need to edit the code so that a new state generates a new Python process and has its own lock? Why did you pick a global lock in the first place (so I understand the hurdles to what I am planning)?

opened by jonathanstrong 1
Split PyType into ToPyType and FromPyType

Split PyType into ToPyType and FromPyType. This is nice to have if you only feel like implementing the conversion in one direction, or if there isn't a logical conversion in one of the directions.

This PR breaks backward compatibility in the public API, so I'd appreciate a second opinion on it.

opened by ghost 1
implement PyRun_* functions

If we implement functions such as PyRun_StringFlags or PyRun_FileFlags, then it would be easy to use embedded python code in projects like video games.

(sorry for stealing #1, I just wanted to say that this could be useful)

opened by sinistersnare 1

Build fails on latest Rust nightly

$ rustc --version
rustc 0.13.0-nightly (96991e933 2014-10-22 23:57:11 +0000)
$ cargo build
   Compiling rustpy v0.1.0 (file:///home/d/Code/rustpy)
src/primtypes.rs:152:5: 152:20 error: cannot infer an appropriate lifetime for autoref due to conflicting requirements
src/primtypes.rs:152     self.as_slice().to_py_object(state)
                         ^~~~~~~~~~~~~~~
src/primtypes.rs:151:3: 153:4 help: consider using an explicit lifetime parameter as shown: fn to_py_object<'a>(&'a self, state: &'a PyState) ->
 Result<PyObject<'a>, PyError>
src/primtypes.rs:151   fn to_py_object<'a>(&self, state : &'a PyState) -> Result<PyObject<'a>, PyError> {
src/primtypes.rs:152     self.as_slice().to_py_object(state)
src/primtypes.rs:153   }
error: aborting due to previous error
Could not compile `rustpy`.

bug

opened by ghost 0