What is your platform? I cannot reproduce on macOS (Ventura, M1) or Linux (Arch Linux, x86_64).

Welcome to the magnificent Rust Python 0.2.0 interpreter 😱 🖖
>>>>> import platform
>>>>> exit()

Oh sorry, I should have said it's when you compile to WASI. I have updated the title.

CC @youknowone

#4964 is similar issue.
I believe _signal is not mendatory for platform. Implementing _signal will be the long term correct goal, but patching python library will also make it working.

What do you mean by patching? Is that something we can do?

Oh, I was not talking about about user-side, but about updating Lib/platform.py from RustPython project to not to refer _signal.
Another point. I think WASI anyway will not support _signal, right? Then maybe a fake _signal module with empty functions like gc will be enough.

I also found platform is updated in python 3.11 not to require _signal when importing. #5060
But still there are encodings problem, so it doesn't work.

oh, it was my mistake. platform will be fixed by #5060

It depends what that signal module does but WASI has a syscall to send signals to the host process, it's proc_raise.

But I think as long as it's mostly empty that's fine or at least if we add what we can support.

Can confirm that importing platform now works 👍 Where would we go to implement things like platform.release()?