Skip to content

Run a Python operator the way the engine runs it #8409

Description

@kz930

Task Summary

A Python operator is not called; it is handed to an interpreter that imports the generated module and drives it through the same open, process and close the engine uses. This step adds PyOpExecHarness, which writes that module, starts the driver, and reads back what the operator emitted.

The driver is the engine's side of the contract written out plainly. It is what makes the answer this side produces the engine's answer rather than an approximation of it.

Third of the twenty-one steps listed in #8325. It stands on its own: it touches no code from the export itself.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions