pyrunfile — Execute a Python file in an isolated script workspace.
pyrunfile(file, ...) executes a Python script. A requested output requires outputNames after file; name-value inputs and an optional Arguments cell of text follow.
Syntax
pyrunfile(file, name, value, ...)
result = pyrunfile(file, outputs, name, value, ...)Inputs
file- Type
StringScalar- Required
- Yes
- Default
- —
- Description
- Python script file.
inputs- Type
Any- Required
- Variadic
- Default
- —
- Description
- Named inputs and optional Arguments cell of script arguments.
outputs- Type
Any- Required
- Yes
- Default
- —
- Description
- Python output name or names, required when an output is requested.
Returns
result- Type
Any- Description
- Python result converted through the session foreign boundary.
Returned values from pyrunfile depend on how many outputs the caller requests.
Errors
RunMat:Foreign:UnsupportedOnWasm- When
- The current host has no explicitly provided CPython capability.
- Message
Python interoperability is unavailable on this host.
RunMat:Foreign:InvalidCall- When
- Arguments do not satisfy the Python interoperability contract.
- Message
Invalid Python interoperability operation.
RunMat:Foreign:HostUnavailable- When
- A Python operation is invoked without an active runtime context.
- Message
Python operation has no active runtime context.
Inputs and execution
The file path is text. Script definitions do not enter the persistent pyrun workspace. Named inputs are passed in pairs; Arguments supplies a cell array of command-line argument text. The script file is read by the Python host and must be available in that host's filesystem. Out-of-process calls suspend while the child executes; callbacks and returned foreign values remain tied to the RunMat session.
Example
Read a named output from a Python file
answer = pyrunfile('answer.py', 'answer', 'input_value', int32(40));
answerExpected output:
answer = 42Using pyrunfile with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how pyrunfile changes the result.
Run a small pyrunfile example, explain the result, then change one input and compare the output.
FAQ
Does a file share pyrun variables?⌄
No. File execution uses a separate script workspace.
Related Interop functions
Native
calllib · clibgen.buildInterface · libfunctions · libisloaded · libpointer · libstruct · loadlibrary · setdatatype · unloadlibrary
Java
isjava · javaaddpath · javaArray · javaclasspath · javaMethod · javaMethodEDT · javaObject · javaObjectEDT · javarmpath · jenv · usejava
Related guides
Source you can read
Every RunMat function's source is public. Read exactly how pyrunfile is executed, line by line, in Rust.
- View the source for pyrunfile in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.
- RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
- Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.