Skip to content

Provide alternate access to Interpreter vm field #4322

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lastmjs opened this issue Dec 9, 2022 · 0 comments
Open

Provide alternate access to Interpreter vm field #4322

lastmjs opened this issue Dec 9, 2022 · 0 comments

Comments

@lastmjs
Copy link

lastmjs commented Dec 9, 2022

Because access to the Interpreter's vm requires a non-async closure, we are forced to find a work-around to enable asynchronous functionality in our project Kybra.

Kybra runs in a strict wasm32-unknown-unknown environment, and for esoteric reasons we believe the non-async closure prevents us from accomplishing what we need to accomplish. To get around this limitation, we've simply made the vm field public in our fork of RustPython.

It would be nice for this change to be upstreamed, or for there to be some way to access the vm without being forced to use a non-async closure.

You can see our fork here with everything we have to do to make RustPython work in our environment: https://github.com/demergent-labs/RustPython/pull/1/files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant