René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Request: normalization and `depythonize`","articleBody":"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).\n\nNow, we are hitting an issue where `I64` values are becoming `U64` after `depythonize`.\n\nI came up with a solution in https://github.com/jamesbraza/tantivy-py/pull/1 that involves re-casting U64 back to I64 if it fits, but this is pretty hacky.\n\nIs there some way to preserve integer types across serialization/deserialization?\n\n- `I64` values remaining `I64`\n- `U64` values remaining `U64`\n\nI am wondering if there is some way `pythonize` can accommodate this, maybe by adding an opt-in flag somewhere?\n\nAlso, I am not 100% sure if this is a `pythonize` vs `pyo3` issue, but it seems to be a deserialization issue, so I opened this here.","author":{"url":"https://github.com/jamesbraza","@type":"Person","name":"jamesbraza"},"datePublished":"2025-03-02T23:11:19.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/80/pythonize/issues/80"}