furb-monty
furb for python, with the engine in monty. furb_monty.engine gives every name of engine.pyi over one life of
the engine in the sandbox of monty, with the Kernel that the crate loads there, so it needs no Kernel of its own.
furb_monty.gate is the gate of the crate, which the package furb reads a word with too.
furb_monty._monty is the door itself, and it gives the same host API as the package of TypeScript, each name in
the case of python. Its Engine has one method for each verb of the contract, which takes the words the verb needs
by position and the others by name, and gives an Act when the verb makes one. _monty.opened(directory=..., record=...) opens a life as every host of the crate opens one: it gives the record and the ears of the crate, which
the host boots after its own ears, and Engine.open(ears, directory=...) boots them at once.
Those ears are the provider of the models, the extensions, which enable at the tip what the configs of the user and
of the directory turn on unless extensions=False, the ear of each official extension, the files, the commands,
time, and the store when the life keeps. Each is a NativeEar, which furb_monty.engine.boot takes beside the
generators of this interpreter, and which the engine of this interpreter, furb.python, steps as a generator of its
own:
from furb_monty import _monty, engine
record, ears = _monty.opened(directory=".", record="life.jsonl", actor="claude-cli:opus")
# `world` is an ear of the host that answers the rest, a prompt to the operator among it.
root = engine.boot(record, world=world, **dict(ears))
The provider offers the model of its actor and the models of its roster, or the first model the catalog offers when
it names neither, and the operator alone when the roster names none and no actor is said. Its answer, a function,
answers each request in place of the models, which the suite of furb does. Its stream, a function, is told what a
model writes as it writes it, its log, a function, is told each report of the life that no model reads, one line
each, in place of the stderr of the process, and images is the directory of the images that a message names. A life that is
inspecting keeps nothing, enables nothing new and asks no model. models(claude) gives the models the catalog of this
machine offers, model(name) one model by its name, and levels() the levels of effort. files(scratch),
bash(scratch, record), time(), store(path), official(), extensions(given), memory(config) and skills(config) give
the ears one by one, as the suite of each extension boots them: the files and the commands share the scratch directory
that the host names, which a word reads as scratch:// and a command as $TMPDIR. Only the opening of a life makes the
files of a record again in its scratch directory, and gives a life with no record a directory that goes with it.
scratch(record) gives the scratch directory of a record, which a host removes when it deletes the record.
answered(shape, line) reads a line of the operator as a value of one of the shapes(), by the rules that every
console of the crate reads a line by. _monty.SYSTEM is the system prompt of every model: the engine, minified with
its program kept as it is.
furb_monty.engine.pending() names the work that an earlier life left, which waits for a wake that this life says,
each act by its name and its kind, as the Engine of the door finds it: among each act that the outside started and
did not end, and the acts that made it, each prompt, rung, command and wait that is not done and that no pause holds.
An act that a wake puts to the outside again is pending no more.
furb_monty.engine.parked() names the work that a crash loop parked, each act by its name and its kind: a run, a
command or a reply that the record shows started in five lives and not done, since each of those lives ended while it
ran. A wake puts no parked act to the outside, so a host that wakes the work of a life as it opens does not run it
again and end again, and a parked act is pending no more. furb_monty.engine.retry(id) runs a parked act again: it is
parked no more in this life, and a wake of it puts it to the outside.
furb_monty.engine.keyed(key, kind, *args, **kwargs) makes the act of a verb once for a key of the client, across a
crash of the host and a retry of the client, as keyed("k1", "prompt", int, "count the lines", on=root). A key fact
goes to the record before the act, and a later call with the same key on the same chain gives the act that the key
made, in this life or in a later life on the record. When the host crashed after it kept the key and before it kept
the act, the call makes the act.
A generator of this interpreter is heard where the engine runs. A verb it says while it hears goes to the life that hears it, as a verb that an ear of the engine of python says does.
FURB_ENGINE=monty makes from furb import engine give furb_monty.engine. The suite of furb runs on both
engines.
The extension module is the crate at the root of the repository, built with its python feature.
Metadata
Release files for furb-monty 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| furb_monty-0.2.0.tar.gz | 14.3 MB | Without provenance | Details for furb_monty-0.2.0.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| furb_monty-0.2.0-cp314-cp314-win_amd64.whl | CPython 3.14 | CPython 3.14 | Windows x86-64 | Details for furb_monty-0.2.0-cp314-cp314-win_amd64.whl |
| furb_monty-0.2.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.14 | CPython 3.14 | Linux glibc 2.17+ x86-64 | Details for furb_monty-0.2.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| furb_monty-0.2.0-cp314-cp314-macosx_11_0_arm64.whl | CPython 3.14 | CPython 3.14 | macOS 11.0+ ARM64 | Details for furb_monty-0.2.0-cp314-cp314-macosx_11_0_arm64.whl |
Total release size: 83.5 MB
Release files / furb_monty-0.2.0.tar.gz
| Download URL | furb_monty-0.2.0.tar.gz |
|---|---|
| Size | 14.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec7adaa33d33c0e9d854b28ae450bc1745df1f99be4bfb82e9cffd93b540325d
|
|
BLAKE2b-256 checksum How to use checksums |
9182e737b7cd694229431b85f7bd9525958986273e467bb3ef620061feb852d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / furb_monty-0.2.0-cp314-cp314-win_amd64.whl
| Download URL | furb_monty-0.2.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 21.8 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
248e197521240b2fd2ad344afa29a01330c08a8d10ad9825da442c146dd8e46c
|
|
BLAKE2b-256 checksum How to use checksums |
35113903e506ef6b3f022fb2aa1729aec20e47161f599a0d5a0a2b670ad26036
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / furb_monty-0.2.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | furb_monty-0.2.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 24.6 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
fbc0d346e2b7663a0b56b058f22bf8d61850df2b20fd5311038e828e785bddcf
|
|
BLAKE2b-256 checksum How to use checksums |
02967333facff749fb66800a02637688249892311bece301bc20817eeac98f74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / furb_monty-0.2.0-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | furb_monty-0.2.0-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 22.8 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
624d2143b6b8bb7e19f10e9884e2d9b6ef2ff05b4c5aa573420d0ed733090f07
|
|
BLAKE2b-256 checksum How to use checksums |
c97b337d8907396a02e1413b283d295d81b75101189fa7cfc0c2b1549e5943b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for furb-monty 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.