Skip to content

PyNext v0.5.0 (experimental)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@Duioolllll Duioolllll released this 06 Nov 15:26
· 243 commits to main since this release
v0.5.0
91af1ca

PyNext v0.5.0 (experimental)

PyNext remains an experimental prototype. It is not a production security boundary and is not compatible with Next.js, React, or React Server Components.

Included

  • Report attempted request throughput separately from successful 2xx throughput, with error rate, status-code distribution, transport errors and p50/p95/p99 latency for all attempts and successes.
  • Report response sizes, process CPU scope and lifetime peak RSS. When benchmarking a separately running local Linux server, optionally sample CPU for its PID and threads.
  • Run the CI suite on Linux, macOS and Windows; build and install a wheel in isolation; save bounded benchmark measurements; and run Chromium end-to-end checks on Linux.
  • Normalize module paths and safely invoke the esbuild Node wrapper on Windows.
  • Update the English, Korean, Japanese and Simplified Chinese manuals.

Manuals

English · 한국어 · 日本語 · 简体中文

PyNext is licensed under MIT. Third-party notices are retained.

Verification

100 Python tests, five Rust tests, Chromium smoke checks, isolated wheel installation and example build. The platform matrix is linked from the release commit's GitHub Actions checks.

Release assets

The source distribution requires supported Python 3.13 and Rust. The attached native wheel is for CPython 3.13 on Linux x86-64 and was verified in the build environment; it is not a universal or manylinux wheel. SHA256SUMS contains checksums. These GitHub assets are not a PyPI publication.

Known limitations

A synchronous handler already executing can continue after a 504 timeout. ISR is process-local. The benchmark's default CPU and peak RSS include the client and server together, and CI records a bounded smoke benchmark without automated performance or memory regression thresholds. Zero-copy, streaming, distributed ISR, React/RSC, OpenTelemetry, worker isolation and standalone packaging are not implemented. See the production roadmap.

Request-body admission issue: In v0.1.0–v0.5.0, slow request bodies can occupy all native execution slots and cause 503 responses. v0.6.0a1 adds a bounded body-read pool and deadline. Header timeouts and total connection limits still require separate controls. Running synchronous handlers can still continue after a 504. These releases remain experimental and should not be exposed directly to the public internet.

Assets 5
Loading