INIT / Install

[GET PYNE RUNNING]

PyPI, source, Docker, or Cloudflare® — pick a path. Operate with CLI, LSP, or Pro API.

Back to PYNEClone on GitHubDocs · Install
Fastest path
pip install "hoox-pyne[lsp,compile]"→pyne --version→pyne check strategy.pyne
[ package ]01PyPIRecommended

Via PyPI

Install hoox-pyne 0.3.12 from PyPI into a virtualenv. Python ≥ 3.10. Preferred bins are pyne and pyne-lsp (aliases pynescript / pynescript-lsp). The import package is pynescript. AGPL v3.

  • ▸Import remains pynescript — never pip install pyne or pip install pynescript (wrong packages).
  • ▸Extras: [lsp] language server, [compile] Numba, [data] CCXT, [pro] Flask Pro API.
  • ▸Prefer .pyne files; .pine remains for TradingView® exports.
  • ▸Not affiliated with TradingView®, Inc.
PyPI hoox-pyne ↗Installation docs
[ package ]02Extras

Optional extras

Layer LSP, Numba compile, CCXT data, and the Flask Pro API on the core hoox-pyne wheel. Install only what the desk needs.

  • ▸LSP is not a CLI subcommand — use pyne-lsp (alias pynescript-lsp).
  • ▸The [compile] extra is required for Numba compile / prewarm / run; --emit works without JIT.
  • ▸The [data] extra is required for CCXT providers on pyne data.
[ source ]03Full StackRecommended

From Source

Clone the language repo, editable-install extras, and run the Flask Pro API locally. Canonical path for contributors who need the full toolchain.

Alt installmake install
  • ▸make run starts the Flask Pro API on :5002.
  • ▸This is the language SoT (hoox-sh/pyne) — not the edge evaluate host.
GitHub Repository ↗Contributing
[ docker ]04GHCR

Docker — CLI

Run the published CLI or LSP image from GHCR without a local Python env. Tagged 0.3.12; published on v* tags.

Build localmake docker-build-cli
  • ▸Image ENTRYPOINT is pynescript (alias of pyne).
  • ▸Non-root appuser. Published on v* tags as ghcr.io/hoox-sh/pyne/{cli,lsp,api}.
[ docker ]05Pro API

Docker — Pro API

Run the Flask Pro API in a container for local or cloud research. Host :5002 maps to container :8080.

  • ▸Flask Pro API for local/cloud research — not the Cloudflare® edge evaluate host.
  • ▸Set ALLOWED_ORIGINS for CORS when AXIS is the client.
[ cloudflare ]06EdgeRecommended

Deploy pyne-worker

Clone hoox-sh/pyne-worker (NOT the language repo). Vendored engine, Cloudflare® R2 OHLCV, POST /run. Not the full toolchain.

  • ▸After engine bumps run ./scripts/sync_vendor.sh before the next deploy.
  • ▸TRADE_SERVICE expects trade-worker — delete that binding if you do not run the HOOX mesh.
  • ▸Worker is evaluate-only (no CLI / LSP). Deploy on Cloudflare® Workers.
pyne-worker docsGitHub pyne-worker ↗Cloudflare® Dashboard ↗
Interfaces

[CLI · LSP · API]

CLI for parse and lint, LSP for editors, Pro API and pyne-worker for evaluate.

CLI

Full ref

Click group · pyne / pynescript

Preferred console script for parse, format, lint, compile, run, and optimize. Same helpers as the library. Alias pynescript.

Parse-only; walks directories

Write back (alias: fmt)

AST dump (alias: ast)

One file or stdin

Python emit; no JIT required

Synthetic OHLCV compile-only

strategy() scripts; interpret Runtime

Version + extras (alias: ls)

LSP

pyne-lsp · stdio

Separate console script — not a Click subcommand. Editors talk stdio to pyne-lsp (alias pynescript-lsp).

pygls extra

Preferred bin

Same entry

PYNE extension

API

Flask Pro · pyne-worker

Evaluate Pine Script™ over HTTP. Desk Flask Pro API or Cloudflare® Workers (pyne-worker) share POST /run.

Flask stack

Flask on :5002

From pyne-worker checkout

  • ▸POST /run, /optimize, /ingest.
  • ▸Authenticate with X-API-Key.
Install paths6
Version0.3.12
Binspyne · pyne-lsp
pip install hoox-pyne → pyne check → evaluate