Repository navigation
Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Python 3.15 legs failed at the wheel build:
[build-system] requireslistedjpype1, JPype 1.7.1 has no cp315 wheel, souv buildcompiled it from source and failed (scikit_build_core ... Unrecognized options in config-settings).Changes
bindings/python/pyproject.toml:build-system.requiresis now["setuptools>=61.0", "wheel"].setup.pyimports onlysetuptools, so the build never needs JPype.buildis a frontend (the workflows andbuild-native.shbring it withuv run --with build), not a backend requirement, so it goes too. The architecture doc excerpt and the Dockerfile comment follow.test-python-bindings.ymlandtest-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 asjpype1 @ 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-pinnedactions/setup-javastep plus anantcheck. The tests still run on the wheel's bundled JRE.ladybughas no cp315 wheel and its sdist needs a C++ build, so the 3.15 requirements leave it out (python_version < "3.15") andtests/conftest.pyleavestest_equivalence_ladybug.pyout of collection on 3.15 (the existingcollect_ignoreconvention, so nothing counts as skipped).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.15inbindings/pythonnow buildsarcadedb_embedded-*-cp315-cp315-linux_x86_64.whlin about 2 s, with no JPype involved.adbc-driver-managerbuilds from its sdist, every other test dependency has a cp315 wheel, and the JVM starts through the git-built JPype.The 3.15 legs stay
experimentalin 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