[pyne-worker]

Production Python Cloudflare Worker for POST /run. Thin wrap over pynescript.runtime. Sister repo — not in this checkout.

pyne-worker

Abstract

pyne-worker is the production edge evaluate host: a Python Cloudflare Worker that vendors pynescript.runtime and speaks the same evaluate contract as Flask POST /run. It is a sister repository — it does not live in this PYNE checkout.

Repohoox-sh/pyne-worker
RoleEdge POST /run + alerts + libraries + cron
RuntimeCloudflare Workers (Python)
EngineVendored hoox-pyne (pynescript.runtime)
In this repo?No

This Worker is a thin wrap. CLI, LSP, Flask Pro API, Numba desk compile, and the language SoT stay in hoox-sh/pyne.

Conceptual model

Interface surface

This WorkerUse PYNE (hoox-pyne) instead
POST /run + alerts + librariespyne CLI, pyne-lsp, VS Code
R2 bars, 1m cron, L2 webhooksFlask Pro API, Docker, /run/batch
Vendored engine (./scripts/sync_vendor.sh)Live package, Numba, corpus harness
30s / 100KB / 100K bars / 5MB envelopeUncapped research on your machine

Taxonomy

NameWhat it is
PYNELanguage SoT (this repo)
PyneTSTypeScript library (@hoox-sh/pynets)
pyne-workerPython Cloudflare evaluate host
pyne-agent-workerNL authoring host (optional validate via this Worker)

Do not create pynescript/pyne-worker/ or pynescript/pine-worker/.

The leftover name pine-worker is a TypeScript Cloudflare experiment (hoox-sh/pine-worker). It is not this host and is not documented on this site. TypeScript library work is PyneTS.

Relationship to PYNE

  • Python Runtime remains the oracle. The Worker vendors a snapshot; it can lag __about__.py.
  • After a PYNE release, operators re-run ./scripts/sync_vendor.sh in the Worker checkout before wrangler deploy.
  • Shared JSON: evaluate contract. Alerts: Alerts.

Quick links

See also