so I run a script python script from rust that has the lines
do_thing_1()
do_thing_2()the result on the Rust side would be a vec![ Action::DoThing1, Action::DoThing2 ]
probably a
pyo3::once_cell::GILOnceCell
Thanks for all the help mejrs, I really appreciate it!
and np 👍
You'd need to use a mutex in general if you want something like that, and pyo3's GILOnceCell in this situation in particular to avoid the possibility of deadlocking
Hey guys. I'm trying to write a simple function with pyo3 and then pack it to the wheel. Here is the function:
use num_bigint::BigUint;
use pyo3::exceptions::PyValueError;
use pyo3::prelude::*;
use pyo3::wrap_pyfunction;
#[pyfunction]
fn product_rust(l: Vec<BigUint>) -> PyResult<BigUint> {
match l.into_iter().reduce(|x, y| x * y) {
Some(val) => Ok(val),
None => Err(PyValueError::new_err("Calculation error"))
}
}But I've got the error:
6 | #[pyfunction]
| ^^^^^^^^^^^^^ the trait `IntoPyCallbackOutput<_>` is not implemented for `Result<BigUint, PyErr>`Does anyone know, how to handle it?
0.4 will be supported with pyo3 0.14. if you are okay with using a git dependency you can do that and use 0.4 of num-bigint right now
1 reply
I'd generally only add
allow_threads when I know the function is going to consume significant CPU time in Rust where another Python thread could be running, or where the function will itself get blocked on io, subprocesses, other mutexes etc
Hello, I'm running the example code in Calling Python in Rust code.
I have all the rust things already, but after I ran cargo run.
It shows:
dyld: Library not loaded: @rpath/libpython3.8.dylib
Referenced from: /Users/slhmy/Workplace/python/python-rust/target/debug/python-rust
Reason: image not found
zsh: abort cargo runI know I can fix it by export LD_LIBRARY_PATH, but actually thing makes me confused is why it choose python3.8 ?
I tried switching version by anacoda or using alias python=..., none of them will effect the version in rust code.
This matters at compile time, not runtime
Do the pyo3-asyncio developers happen to drop by here every once in awhile? Wanted to bounce some ideas around that are probably better in discussion than an issue.
Hm, I'm probably missing something obvious. When you have a
I'm basically looking for self.getattr(). Something like:
#[pyclass], in a method of that class, how does one get the Python instance of self?I'm basically looking for self.getattr(). Something like:
python_class.call_method1("add_callback", (self.getattr("callback_method"),));
https://docs.rs/pyo3/0.13.2/pyo3/ffi/struct.PyType_Spec.html#structfield.flags shouldn't the flags field be a
c_int?
Hmm looks like it is actually a uint in the Python c source: https://github.com/python/cpython/blob/62f1d2b3d7dda99598d053e10b785c463fdcf591/Include/object.h#L224
makes you feel grateful for rustdoc and rendering docs from source :)
Hey everyone.
Can someone point me to the source of this book(https://pyo3.rs/v0.13.2/) ? I would like to contribute to a chapter but I am unable to find the github link for this.
Can someone point me to the source of this book(https://pyo3.rs/v0.13.2/) ? I would like to contribute to a chapter but I am unable to find the github link for this.
You can have it as a field, you just cant directly expose it
that's fine, I only interact with the field on the Rust side
thanks
Or downcast if you want to convert to PyString
If anyone is looking for speedups for msgpack, check out my new library - https://github.com/aviramha/ormsgpack