Repository navigation
Conversation
…d requirements setup.py imports only setuptools, so the wheel build needs no JPype. On Python 3.15 JPype 1.7.1 has no cp315 wheel, so listing jpype1 in build-system.requires (and in the Dockerfile build-tools install) makes the build compile it from source, which fails. Verified with `uv build --wheel --python 3.15`. 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.
On Python 3.15 the wheel build fails:
[build-system] requireslistsjpype1, JPype 1.7.1 has no cp315 wheel (it has cp38 to cp314), so the isolated build environment compiles JPype from source and fails (scikit_build_core ... Unrecognized options in config-settings). JPype master supports 3.15 (jpype-project/jpype#1493, #1498, #1501) but has not released.Changes
pyproject.toml:build-system.requiresis now["setuptools>=61.0", "wheel"].setup.pyimports onlysetuptools, so the build never needs JPype.buildis a frontend, not a backend requirement, so it goes too.scripts/Dockerfile.build: the build-tools install dropsjpype1for the same reason (python:3.15-slimhas no compiler, so it would fail there too).build,wheelandsetuptoolsstay.No other line is touched, to stay clear of the open CI and rename branches.
Checked locally
uv build --wheel --python 3.15(Python 3.15.0) now buildsarcadedb_embedded-*-cp315-cp315-linux_x86_64.whlin about 2 s.Not in this PR
mainhas no Python 3.15 leg today (the test and examples matrices stop at 3.14). Adding one needs JPype from a pinned master commit in the test environment until JPype publishes cp315 wheels, andladybughas no cp315 wheel either. humemai/arcadedb-embedded-python#511 does that for its workflows and can be ported once this lands.🤖 Generated with Claude Code