"static type has not been initialized" when type lives in another module about rustpython HOT 3 OPEN

FWIW I ran into this same problem trying to add typing to the stdlib. After several hours of digging I found the essential_init phase of the vm initialization process.

I think the only real way to improve this discovery process is documentation. Either an example which covers this use case (with useful comments), or some documentation on all the magical [py*] macros.

from rustpython.

static types are initializable in Rust side code. So python code doesn't provide that much information.

Technically it means StaticType::init_builtin_types is not called for the type. It is usually called by <module_name>::make_module() if you created a module named <module_name> with #[pymodule].

One of the possible reason can be separated but not initialized python modules. If you created modules named A and B, referencing A::SomeType in B, running code including B but didn't run A::make_module() yet.

from rustpython.

Do you have any advice to make this less confusing?

from rustpython.