pythonize
pythonize copied to clipboard
POC about can we keep a `&Bound` and not a `Bound` to deserialize.
serde advice to name serializer and deserializer respectively to_ and from_. `pythonize` => `to_pyobject` `depythonize_bound` => `from_bound`
Simple update to PyO3 version 0.24.
Ran into an issue with x86 where heavily nested data was causing a segmentation fault on depythonize. Issue came from using sqloxide to get ast for queries, narrowed it down...
When upgrading `pythonize` from version `0.21.0` to version `0.23.0` in `tantivy-py`'s https://github.com/quickwit-oss/tantivy-py/pull/401, we switched from `extract` to `extract_bound` (per https://github.com/PyO3/pyo3/pull/3916). Now, we are hitting an issue where `I64` values are...
MCVE: Rust side: ```rs #[derive(Deserialize)] struct Foo { #[serde(default)] foo: bool, } ``` python side: ```python foo = { "foo": None, } ``` `depythonize::(...)` will fail with `unexpected type: 'NoneType'...