pydeno 0.4.0__tar.gz

pydeno-0.4.0/.github/workflows/benchmarks.yml

@@ -0,0 +1,32 @@
+name: Benchmarks
+
+# Informational only -- reports numbers in the log/summary, never fails the build.
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  benchmarks:
+    # macos-latest: the Linux cdylib build currently fails to link V8 (rust-lld
+    # TLS relocation vs -shared, tracked separately, pre-existing/unrelated to
+    # benchmarking) -- same failure as the v0.1.0 Linux wheel build.
+    runs-on: macos-latest
+    steps:
+      - uses: actions/checkout@v5
+
+      - uses: astral-sh/setup-uv@v7
+
+      - name: Rust benchmarks (Criterion)
+        run: cargo bench --features bench | tee -a "$GITHUB_STEP_SUMMARY"
+
+      - name: Build release extension
+        run: |
+          uv sync --group all
+          uv run maturin develop --uv --release
+
+      - name: Python benchmarks (pytest-benchmark)
+        run: uv run pytest benches_py/ --benchmark-only | tee -a "$GITHUB_STEP_SUMMARY"

pydeno-0.4.0/.github/workflows/docs.yml

@@ -0,0 +1,58 @@
+name: Documentation
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - "docs/**"
+      - "mkdocs.yml"
+      - "python/pydeno/**"
+      - ".github/workflows/docs.yml"
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.x"
+
+      - uses: astral-sh/setup-uv@v7
+
+      - name: Install dependencies
+        run: uv sync --no-install-project --group docs
+
+      - name: Build documentation
+        run: source .venv/bin/activate && mkdocs build
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v4
+        with:
+          path: ./site
+
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

pydeno-0.4.0/.github/workflows/test.yml

@@ -0,0 +1,229 @@
+name: Tests
+
+# The first workflow in this repo that actually runs the test suite. Before
+# this, `.github/workflows/` held only publish-on-release, benchmarks and
+# docs, so every "the tests pass" claim was local and unverified.
+on:
+  push:
+  pull_request:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: tests-${{ github.ref }}
+  cancel-in-progress: true
+
+env:
+  # A `>=` floor on the collected test count, not an equality check: adding
+  # tests never needs a bump here, only deleting them does. This is the
+  # assertion that makes a mass-skip fail the job -- see
+  # `scripts/check_test_report.py` for the full rationale.
+  MIN_PYTHON_TESTS: "553"
+  # Skips are unverified tests, so the budget is zero. The suite has exactly
+  # one conditional skip (`tests/test_idle_cpu.py`, skipped above 16 CPUs) and
+  # GitHub's macOS runners are well under that, so zero is correct here. Every
+  # skip is printed with its reason regardless, so a new one is visible before
+  # anyone tolerates it.
+  MAX_SKIPPED: "0"
+  CARGO_TERM_COLOR: always
+
+jobs:
+  # Debug and release are separate jobs on purpose. The library's headline
+  # invariant -- guest JS gets a result or a catchable exception, never a host
+  # crash -- silently depended on `-O` shrinking the recursive serializer's
+  # stack frames: `rt.eval("[" * 80 + "]" * 80)` killed the process on a debug
+  # build and was refused cleanly on a release build. A release-only CI job
+  # cannot see that class of bug at all.
+  pytest:
+    name: pytest (${{ matrix.profile }})
+    # macos-latest, matching `benchmarks.yml`: the Linux cdylib build currently
+    # fails to link V8 (rust-lld TLS relocation vs `-shared`), a pre-existing
+    # issue tracked separately. Moving these jobs to Linux is a follow-up, and
+    # would want a `manylinux: 2_28` container -- the pinned `deno_core`'s V8
+    # needs glibc >= 2.27.
+    #
+    # State this plainly, because it is the largest remaining hole in the
+    # verification story: `workflow.yaml` publishes `manylinux_2_28` wheels
+    # that **no CI job ever imports, let alone tests**. The wheel is built in
+    # maturin-action's container (which does link), so what is missing is not
+    # the build but a job that installs the built wheel and runs `pytest`
+    # against it. Until that exists, every Linux claim in this repo rests on
+    # the container producing a wheel, not on anything having run it.
+    runs-on: macos-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - profile: debug
+            maturin_args: ""
+          - profile: release
+            maturin_args: "--release"
+    steps:
+      - uses: actions/checkout@v5
+
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+
+      - uses: Swatinem/rust-cache@v2
+        with:
+          key: ${{ matrix.profile }}
+
+      - name: Build the extension (${{ matrix.profile }})
+        run: |
+          uv sync --frozen --group all
+          uv run maturin develop --uv ${{ matrix.maturin_args }}
+
+      # Collection is a separate step so a collection error (which removes
+      # every test in the offending file) fails the job on its own exit code,
+      # before anything has had a chance to look green.
+      - name: Collect tests
+        run: |
+          uv run python -m pytest tests/ --co -q \
+            -p no:randomly --strict-markers --strict-config \
+            | tee collect-${{ matrix.profile }}.log
+
+      - name: Run pytest
+        # `continue-on-error` is deliberate: a red suite must still reach the
+        # report check below, which is what turns "the process died at test 46"
+        # into a legible error instead of a bare exit code.
+        continue-on-error: true
+        id: pytest
+        run: |
+          uv run python -m pytest tests/ -v \
+            -p no:randomly --strict-markers --strict-config \
+            --junitxml=junit-${{ matrix.profile }}.xml
+
+      - name: Check the test report for skipped or unrun tests
+        run: |
+          uv run python scripts/check_test_report.py \
+            --label "pytest ${{ matrix.profile }}" \
+            --junit junit-${{ matrix.profile }}.xml \
+            --collect-log collect-${{ matrix.profile }}.log \
+            --min-tests "$MIN_PYTHON_TESTS" \
+            --max-skipped "$MAX_SKIPPED"
+
+      - name: Fail if pytest itself failed
+        if: steps.pytest.outcome != 'success'
+        run: |
+          echo "::error::pytest exited non-zero in the ${{ matrix.profile }} profile"
+          exit 1
+
+  # Closes the gap the `pytest` job's comment above states plainly:
+  # `workflow.yaml` publishes `manylinux_2_28` wheels that no CI job ever
+  # imported, let alone tested. This job builds that exact wheel (same
+  # `manylinux: 2_28` as `workflow.yaml`) and actually installs + imports +
+  # tests it on Linux, instead of resting every Linux claim on "the
+  # container produced a wheel".
+  pytest-linux-wheel:
+    name: pytest (linux wheel)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+
+      - uses: Swatinem/rust-cache@v2
+        with:
+          key: linux-wheel
+
+      - name: Build a manylinux_2_28 wheel
+        uses: PyO3/maturin-action@v1
+        with:
+          args: --release --out dist --find-interpreter
+          manylinux: 2_28
+
+      - name: Install the built wheel (not the editable dev build)
+        run: |
+          uv venv .wheel-venv
+          # `--find-interpreter` builds one wheel per CPython minor found in
+          # the manylinux container (cp310..cp313), so `dist/*.whl` expands to
+          # several and `uv pip install` refuses them: "Requirements contain
+          # conflicting URLs for package `pydeno`". Install only the wheel
+          # whose ABI tag matches this venv's interpreter.
+          PYTAG=$(.wheel-venv/bin/python -c \
+            'import sys; print("cp%d%d" % sys.version_info[:2])')
+          WHEEL=$(ls dist/*-${PYTAG}-${PYTAG}-*.whl)
+          echo "Installing $WHEEL into a $PYTAG venv"
+          uv pip install --python .wheel-venv/bin/python "$WHEEL"
+          # Matches the `testing` dependency group in pyproject.toml -- the
+          # test *runner's* deps, deliberately installed on top of the built
+          # wheel rather than an editable `maturin develop` install.
+          uv pip install --python .wheel-venv/bin/python \
+            "pytest>=8.4.0" "pytest-asyncio>=1.2.0" "hypothesis>=6.100.0"
+
+      # Same collection-first-then-run-then-check shape as the macOS jobs, so
+      # a collection error or a mass-skip fails this job exactly as loudly.
+      - name: Collect tests
+        run: |
+          .wheel-venv/bin/python -m pytest tests/ --co -q \
+            -p no:randomly --strict-markers --strict-config \
+            | tee collect-linux-wheel.log
+
+      - name: Run pytest against the installed wheel
+        continue-on-error: true
+        id: pytest
+        run: |
+          .wheel-venv/bin/python -m pytest tests/ -v \
+            -p no:randomly --strict-markers --strict-config \
+            --junitxml=junit-linux-wheel.xml
+
+      - name: Check the test report for skipped or unrun tests
+        run: |
+          uv run python scripts/check_test_report.py \
+            --label "pytest linux-wheel" \
+            --junit junit-linux-wheel.xml \
+            --collect-log collect-linux-wheel.log \
+            --min-tests "$MIN_PYTHON_TESTS" \
+            --max-skipped "$MAX_SKIPPED"
+
+      - name: Fail if pytest itself failed
+        if: steps.pytest.outcome != 'success'
+        run: |
+          echo "::error::pytest exited non-zero against the installed linux wheel"
+          exit 1
+
+  cargo-test:
+    name: cargo test
+    runs-on: macos-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: Swatinem/rust-cache@v2
+
+      # `--test-threads=1` is this repo's convention: several tests share
+      # process-global V8 platform state, and the Rust suite is not safe to
+      # interleave.
+      - name: cargo test
+        run: cargo test --release --features bench -- --test-threads=1
+
+  lint:
+    name: lint
+    runs-on: macos-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+      - uses: Swatinem/rust-cache@v2
+
+      - name: cargo fmt
+        run: cargo fmt --all -- --check
+
+      - name: cargo clippy
+        run: cargo clippy --tests -- -D warnings
+
+      # Pinned. `uv tool run ruff` resolves the newest release at job time, so
+      # an unpinned lint step turns every upstream ruff release into a red
+      # build that nobody in this repo caused: 0.16 widened the default rule
+      # selection and reports 248 findings (I001, PYI048, PIE790, SIM117, ...)
+      # against `main` @ 400e3cb, none of them regressions. Bumping the pin is
+      # then a deliberate commit that clears the new rules, which is what a
+      # lint gate is for.
+      - name: ruff check
+        run: uv tool run ruff@0.15.10 check python/pydeno tests scripts
+
+      - name: ruff format
+        run: uv tool run ruff@0.15.10 format --check python/pydeno tests scripts

pydeno-0.4.0/.github/workflows/workflow.yaml

@@ -0,0 +1,127 @@
+name: Publish to PyPI
+
+# Runs only when a GitHub Release is published -- never on every push.
+# Actually publishing requires PyPI Trusted Publishing to be configured for
+# this exact repo + workflow on the PyPI project page first (see README).
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  linux:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        target: [x86_64]
+    steps:
+      - uses: actions/checkout@v5
+      - name: Build manylinux wheels
+        uses: PyO3/maturin-action@v1
+        with:
+          target: ${{ matrix.target }}
+          args: --release --out dist --find-interpreter
+          # v8 >=150.1 (pulled in via deno_core >=0.409, see Cargo.toml) needs
+          # glibc's memfd_create (glibc >=2.27), which manylinux2014's glibc
+          # 2.17 lacks ("auto" resolved to manylinux2014 and the resulting
+          # wheel failed to import: "undefined symbol: memfd_create").
+          # manylinux_2_28 ships glibc 2.28.
+          manylinux: 2_28
+      - uses: actions/upload-artifact@v4
+        with:
+          name: wheels-linux-${{ matrix.target }}
+          path: dist
+
+  macos:
+    runs-on: macos-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: PyO3/maturin-action@v1
+        with:
+          args: --release --out dist --find-interpreter
+      - uses: actions/upload-artifact@v4
+        with:
+          name: wheels-macos
+          path: dist
+
+  windows:
+    runs-on: windows-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: PyO3/maturin-action@v1
+        with:
+          args: --release --out dist --find-interpreter
+      - uses: actions/upload-artifact@v4
+        with:
+          name: wheels-windows
+          path: dist
+
+  sdist:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: PyO3/maturin-action@v1
+        with:
+          command: sdist
+          args: --out dist
+      - uses: actions/upload-artifact@v4
+        with:
+          name: wheels-sdist
+          path: dist
+
+  # `test.yml`'s `pytest-linux-wheel` job runs this same check on every
+  # push/PR, but a `needs:` dependency only works within one workflow file,
+  # so a release can't lean on that job directly. This job re-runs the same
+  # gate -- install the manylinux_2_28 wheel this release is about to
+  # publish and actually `import`+test it -- against the artifact the
+  # `linux` job above just built, so `publish` cannot ship a wheel that was
+  # never installed anywhere.
+  test-linux-wheel:
+    name: Test the linux wheel before publishing
+    needs: [linux]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+      - uses: actions/download-artifact@v6
+        with:
+          name: wheels-linux-x86_64
+          path: dist
+      - name: Install the wheel and run the suite against it
+        run: |
+          uv venv .wheel-venv
+          # Same as `test.yml`'s `pytest-linux-wheel`: the `linux` job's
+          # `--find-interpreter` produces one wheel per CPython minor, so a
+          # bare `dist/*.whl` is a multi-wheel glob that `uv pip install`
+          # rejects. Pick the one matching this venv's ABI tag.
+          PYTAG=$(.wheel-venv/bin/python -c \
+            'import sys; print("cp%d%d" % sys.version_info[:2])')
+          WHEEL=$(ls dist/*-${PYTAG}-${PYTAG}-*.whl)
+          echo "Installing $WHEEL into a $PYTAG venv"
+          uv pip install --python .wheel-venv/bin/python "$WHEEL"
+          uv pip install --python .wheel-venv/bin/python \
+            "pytest>=8.4.0" "pytest-asyncio>=1.2.0" "hypothesis>=6.100.0"
+          .wheel-venv/bin/python -m pytest tests/ -q \
+            -p no:randomly --strict-markers --strict-config
+
+  publish:
+    name: Publish to PyPI (Trusted Publishing)
+    needs: [linux, macos, windows, sdist, test-linux-wheel]
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/pydeno
+    permissions:
+      id-token: write  # required for PyPI Trusted Publishing (OIDC) -- no API token secret needed
+    steps:
+      - uses: actions/download-artifact@v6
+        with:
+          pattern: wheels-*
+          path: dist
+          merge-multiple: true
+      - name: Publish
+        uses: pypa/gh-action-pypi-publish@release/v1

pydeno-0.4.0/.gitignore

@@ -0,0 +1,80 @@
+/target
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+.pytest_cache/
+*.py[cod]
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+.venv/
+env/
+bin/
+build/
+develop-eggs/
+dist/
+eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+include/
+man/
+venv/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+pip-selfcheck.json
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.coverage
+.cache
+nosetests.xml
+coverage.xml
+
+# Translations
+*.mo
+
+# Mr Developer
+.mr.developer.cfg
+.project
+.pydevproject
+
+# Rope
+.ropeproject
+
+# Django stuff:
+*.log
+*.pot
+
+.DS_Store
+
+# Sphinx documentation
+docs/_build/
+
+# mkdocs build output
+site/
+
+# Tool caches
+.ruff_cache/
+.hypothesis/
+.benchmarks/
+
+# PyCharm
+.idea/
+
+# VSCode
+.vscode/
+
+# Pyenv
+.python-version