Skip to content

ci: Python 3.15 leg builds the wheel and tests with JPype from a pinned master commit - #511

Merged
tae898 merged 1 commit into
mainfrom
ci-py315
Oct 24, 2026
Merged

tae898 merged 1 commit into
mainfrom
ci-py315

Conversation

@tae898

@tae898 tae898 commented Oct 24, 2026

Copy link
Copy Markdown

The Python 3.15 legs failed at the wheel build: [build-system] requires listed jpype1, JPype 1.7.1 has no cp315 wheel, so uv build compiled it from source and failed (scikit_build_core ... Unrecognized options in config-settings).

Changes

  • bindings/python/pyproject.toml: build-system.requires is now ["setuptools>=61.0", "wheel"]. setup.py imports only setuptools, so the build never needs JPype. build is a frontend (the workflows and build-native.sh bring it with uv run --with build), not a backend requirement, so it goes too. The architecture doc excerpt and the Dockerfile comment follow.
  • test-python-bindings.yml and test-python-examples.yml: for Python 3.15 only, the test environment installs JPype from a pinned commit of jpype-project/jpype master (ed2cc20, 2026-10-19, includes the 3.15 support from jpype#1493, build(deps): bump org.mockito:mockito-core from 5.10.0 to 5.11.0 ArcadeData/arcadedb#1498 and feat: implement ALTER TYPE oldName NAME newName operation ArcadeData/arcadedb#1501), written as jpype1 @ git+https://github.com/jpype-project/jpype@<sha> ; python_version >= "3.15", so other versions are untouched. Building JPype needs a JDK (jni.h, javac) and Apache Ant, so the 3.15 leg gets a SHA-pinned actions/setup-java step plus an ant check. The tests still run on the wheel's bundled JRE.
  • ladybug has no cp315 wheel and its sdist needs a C++ build, so the 3.15 requirements leave it out (python_version < "3.15") and tests/conftest.py leaves test_equivalence_ladybug.py out of collection on 3.15 (the existing collect_ignore convention, so nothing counts as skipped).
  • Every temporary line carries REMOVE WHEN: jpype1 publishes cp315 wheels (JPype > 1.7.1) (or the ladybug equivalent).

Checked locally (Python 3.15.0 via uv, cores 0-3)

  • uv build --wheel --python 3.15 in bindings/python now builds arcadedb_embedded-*-cp315-cp315-linux_x86_64.whl in about 2 s, with no JPype involved.
  • The CI test requirements resolve under 3.15: JPype master builds in about 7 s with Temurin 17 and Ant 1.10.15 (version 1.7.2.dev0), adbc-driver-manager builds from its sdist, every other test dependency has a cp315 wheel, and the JVM starts through the git-built JPype.
  • actionlint is clean on both workflows; pre-commit passes on the changed files.

The 3.15 legs stay experimental in this PR until the run on this branch shows whether they pass. If they do, the follow-up commit here removes the flag.

🤖 Generated with Claude Code

…ed master commit

The wheel build compiled jpype1 from source on 3.15 (build-system.requires listed it, and JPype 1.7.1 has no cp315 wheel) and failed. setup.py imports only setuptools, so jpype1 and the unused `build` package leave build-system.requires.

For the test environment, 3.15 installs JPype from a pinned commit of master (it supports 3.15), built with the runner JDK and Ant. ladybug has no cp315 wheel, so 3.15 leaves it and its equivalence test out.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@tae898
tae898 merged commit 78e97b1 into main Oct 24, 2026
42 of 44 checks passed
@tae898
tae898 deleted the ci-py315 branch October 24, 2026 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant