Standalone binaries for machines without Python

Aperta
  • Qualcosa non va?
#60 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
6/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python, wasm
Ambito
cli, devops, devtools

Direzione di ricerca

Start with the design questions listed in the issue body: the target matrix, the size and startup budget, and the signing approach, and read docs/versioning.md for the 1.x stability rules. Nothing is implemented yet, so the first step is a design comment in this issue, not code. Done means the design is agreed here, a tagged release publishes checksummed binaries for the agreed matrix, the README documents the download path, and devready --version runs on each target.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement help wanted

Problem: Every install path needs Python tooling or Node: pipx, uvx, pip, or npm (which shells out to uvx/pipx). The machine DevReady is meant to diagnose may have none of them, so the tool cannot run where it is needed most.

Do (design first, then implement):

  • Open a short design discussion in this issue before writing the release pipeline. Compare at least:
    • PyInstaller / Nuitka one-file builds,
    • a self-contained Python distribution (python-build-standalone) plus a launcher,
    • a small native launcher that downloads a pinned wheel.
  • Decide and document:
    • target matrix (Windows x64/arm64, macOS arm64/x86_64 or universal, Linux x86_64/aarch64),
    • size and startup-time budget (the current install is a sub-second pure-Python package),
    • signing/notarization (Windows Authenticode, macOS Developer ID) and checksums,
    • antivirus false positives and how the docs will phrase them,
    • what happens to the "zero runtime dependencies" principle.
  • Then add a release job (or a separate build-binaries.yml) that attaches archives to the GitHub release, plus README install instructions and a devready --version smoke test per target.

Done when:

  • The design section is agreed in this issue and reflects the 1.x stability rules in docs/versioning.md.
  • A tagged release publishes binaries for the agreed matrix, each with a checksum.
  • README documents the download path next to pipx, uvx and npm.
  • The existing CLI output, exit codes and check ids are unchanged.

Notes:

  • This is not a good-first-issue: it touches release infrastructure and possibly paid signing accounts.
  • Do not add a network call to the CLI itself; binaries are just another way to ship the same package.
Lingua principale
Python
Stelle
2
Fork
3
Merge medio
10h 51m
PR unite (30g)
40

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Evalogical-Inc/devReady

Tutte le issue di Evalogical-Inc/devReady

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.