Reading .pyc, .so, .dll y .pyd

Want to use RustPython before the new year

Detailed Explanation

Hi, I have a new year's wish to ask the RustPython Team.

I was thinking of using RustPython as an alternative to CPython for Christmas. But it turns out that RustPython does not offer an alternative to ctypes such as a ffi library that connects to rust (at least).

Drawbacks, Rationale, and Alternatives

If RustPython does not read its own .pyc files, they will only serve to waste space in the memory of its users' PCs, making them more annoying than they already are for those who do not use them (such as students and people who are testing for bugs).

By not reading .so and .dll (Libraries) RustPython is at a disadvantage to other Python implementations that can read Libraries.

By not reading .pyd and .so (Pyhon extensions) RustPython is at a disadvantage to other Python implementations that can read Python extensions.

I love Rust and I love Python with pyo3 (a crate) I can make them work together. With RustPython Rust rules and barely leaves room for almost unnecessary Python co-existence (that's what I think after doing so much code in Rus and Little in Python using RustPython source code).

CPython can coexistence at the same time or at different times with Go (Golang), Rust, C++, C, Ruby and others. With RustPython this coexistence does not exist.

Unresolved Questions

Maybe I'm a little rough but:

1. Why doesn't RustPython read the bytecode files it creates?

2. Why doesn't RustPython read .so, .dll, .pyc, .pyd, .so (equivalent to .pyd of Windows for Linux) files?

3. Don't you think it's time RustPython reads .so and .dll like Python does with ctypes, well, also .pyd and .so.