> to also be constrained by a separate set of data types which are legal in rust. This isn't really how writing rust/python iterop works. You tend to have opaq

> to also be constrained by a separate set of data types which are legal in rust. This isn't really how writing rust/python iterop works. You tend to have opaque handles you call python methods on. Here's a decent example I found skimming the code. https://github.com/pydantic/pydantic-core/blob/main/src/input/input_python.rs#L157 https://github.com/pydantic/pydantic-core/blob/main/src/inpu...