Skip to content

Provide alternate access to Interpreter vm field #4322

@lastmjs

Description

@lastmjs

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions