- harness/es.py: append-only event store + проекции (образец — кооп-портал) - harness/levels.py: уровни 1с/1м/1ч/1д, контекст ∝ масштабу - harness/scheduler.py: уровневые потоки, идемпотентные тики, absorbed-стабы - harness/isolated_runner.py + _llm_worker.py: LLM-тик в сабпроцессе (глобальный asyncio-рантайм Strands не переживает 2+ create_harness) - cli.py: init/task/tasks/status/events + requeue (написан самим минутным агентом) - 9router: отдельный ключ sk-simbiot, модель auto (glm-5.3 первым)
73 lines
2.7 KiB
Text
73 lines
2.7 KiB
Text
Metadata-Version: 2.4
|
|
Name: pydantic-monty-runtime
|
|
Version: 0.0.23
|
|
Classifier: Development Status :: 3 - Alpha
|
|
Classifier: Programming Language :: Rust
|
|
Classifier: Intended Audience :: Developers
|
|
Classifier: License :: OSI Approved :: MIT License
|
|
Classifier: Operating System :: Unix
|
|
Classifier: Operating System :: POSIX :: Linux
|
|
Classifier: Operating System :: Microsoft :: Windows
|
|
Classifier: Environment :: MacOS X
|
|
Summary: The monty CLI binary — spawned as worker subprocesses by pydantic-monty
|
|
Home-Page: https://github.com/pydantic/monty/
|
|
License: MIT
|
|
Requires-Python: >=3.10
|
|
Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
|
|
Project-URL: Homepage, https://github.com/pydantic/monty
|
|
Project-URL: Source, https://github.com/pydantic/monty
|
|
|
|
# pydantic-monty-runtime
|
|
|
|
The `monty` command-line binary for the
|
|
[Monty](https://github.com/pydantic/monty) sandboxed Python interpreter.
|
|
|
|
Installing the wheel puts the compiled binary in the environment's scripts directory.
|
|
|
|
You normally don't install this directly — the
|
|
[`pydantic-monty`](https://pypi.org/project/pydantic-monty/) metapackage pulls
|
|
it in alongside the Python bindings, which need it to spawn worker
|
|
subprocesses. Install it on its own to get just the CLI, or to supply the binary
|
|
to an existing [`pydantic-monty-client`](https://pypi.org/project/pydantic-monty-client/)
|
|
install:
|
|
|
|
```bash
|
|
uv add pydantic-monty-runtime
|
|
# or
|
|
pip install pydantic-monty-runtime
|
|
```
|
|
|
|
Or to install the `monty` binary as a tool
|
|
|
|
```bash
|
|
uv tool install pydantic-monty-runtime
|
|
monty --help
|
|
```
|
|
|
|
## Usage
|
|
|
|
- `monty` — start an interactive REPL
|
|
- `monty file.py` — run a Python file
|
|
- `monty -c "<code>"` — run a program passed as a string (like `python -c`)
|
|
- `-i` / `--interactive` — run the file or `-c` program in a REPL session
|
|
(like `python -i`)
|
|
- `-t` / `--type-check` — type check (powered by [ty](https://docs.astral.sh/ty/))
|
|
before executing
|
|
- `--type-check-format` — diagnostic format: `full` (default), `concise`,
|
|
`json`, `github` and the other ty formats (requires `--type-check`)
|
|
- `-m` / `--mount /host/path::/virtual/path[::mode[::write_limit_bytes]]` —
|
|
mount a host directory into the sandbox (`ro`, `rw`, or `overlay`)
|
|
- `--max-memory 10MB`, `--max-duration 0.5`, `--max-recursion-depth`,
|
|
`--gc-interval`, `--max-suspensions` — sandbox resource limits
|
|
|
|
## Worker mode
|
|
|
|
`monty subprocess` runs the binary as a wire-protocol child: framed protobuf
|
|
requests on stdin, framed events on stdout. This is how `pydantic-monty` runs
|
|
sandboxed code with crash isolation, and is meant to be driven by a parent
|
|
process, not by hand.
|
|
|
|
The wheels are built from the
|
|
[`monty-runtime`](https://crates.io/crates/monty-runtime) crate; see its
|
|
readme for cargo features, telemetry, and the rest of the Rust-side detail.
|
|
|