You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CI: test Python 3.15 in the full matrix of both wheels once jpype1 and ladybug ship cp315 wheels #350
The native wheel lists 3.15, but only the pyver subset job tests it, without the files that need jpype1. arcadedb-jvm is capped at <3.15 because JPype has no 3.15 wheel.
On PyPI today, jpype1 1.7.1 has no cp315 wheel. JPype added 3.15 to its matrix in jpype-project/jpype#1501 (merged 2026-10-12) and has not released since. ladybug 0.22.3 has cp310 to cp314 wheels only (request: LadybugDB/ladybug#1465).
Proposal
I keep this open as the tracker and make the move in one PR when both projects publish cp315 wheels.
Not covered
Free-threaded 3.15t, and anything before those wheels exist.
Checklist
native: 3.15 moves from PYVER_ONLY_PYTHONS and NO_JPYPE_PYTHONS into ALL_PYTHONS; the Python list in verify of release-native.yml follows
JVM: drop the cap, add the classifier, add 3.15 to PYTHONS in scripts/select_matrix.py, fix tests/test_select_matrix.py
jpype1>=<first cp315 release>; python_version >= "3.15", so 3.15 never builds JPype from source
install, which-package and CI pages, README
I can run the JVM suite on 3.15 against JPype master and report on jpype-project/jpype.
Activity