Currently, the Rust-space QPY load always attaches to a Python interpreter if it needs to create a Python-space object to load a file. We can't safely expose QPY to C while this is baked-in behaviour; we should add an option to instead error out if a file would require Python to load.
This may come after #15662.
Currently, the Rust-space QPY load always attaches to a Python interpreter if it needs to create a Python-space object to load a file. We can't safely expose QPY to C while this is baked-in behaviour; we should add an option to instead error out if a file would require Python to load.
This may come after #15662.