Support Python 3.15 and free-threaded 3.15t
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
Research direction
Start by reading the Python test environment definitions and CI configuration for the existing 3.14 environments, then review the named failing tests in xarray/testing/assertions.py and the test guards described in the report. Compare the proposed 3.15 and 3.15t environments with those setups and investigate the scipy file manager race. Done means the new environments and fixes are ready for CI, with the reported failures addressed.
Written by the indexing model from the issue text.
Description
Python 3.15.0 is out, and conda-forge has both python-gil and python-freethreading builds. I tried running the test suite on both, as preparation for adding them to CI.
Python 3.15 (conda-forge)
- All test dependencies have 3.15 builds except pyarrow.
- The
daskmetapackage requires pyarrow, so without a lower bound the solver silently falls back to dask/distributed 2023.3.0. Usingdask-core >=2026+distributedinstead gives dask 2026.8.0, and otherwise the same versions astest-py314. - Test results: 1 failed, 22016 passed.
TestDataArray::test_to_dask_dataframeneeds pyarrow (viadask.dataframe) but is only guarded byrequires_dask.
Free-threaded Python 3.15t (PyPI wheels)
conda-forge has no free-threaded 3.15 builds of numpy, pandas, scipy etc. yet, but PyPI has cp315t wheels for numpy, pandas, scipy, pyarrow, matplotlib, cartopy, rasterio and lxml. There are no cp315t wheels for cftime, netCDF4, h5py, numcodecs, bottleneck, numexpr and numba.
With a conda python-freethreading interpreter and PyPI wheels: 150 failed, 2 errors, 14646 passed. With PYTHON_GIL=1, 148 of these still fail, so most aren't free-threading issues:
- 137: h5netcdf is installed without h5py (no
cp315twheel), sorequires_h5netcdfdoesn't skip. Environment issue. - 5:
test_ensure_warnings_not_elevated.ensure_warningsinxarray/testing/assertions.pyreassignswarnings.filters, which has no effect with context-aware warnings (sys.flags.context_aware_warnings, on by default in free-threaded builds). So the publicxr.testing.assert_*functions elevate warnings to errors there. - 3:
test_rechunk_multi_dimensional_da_cftimeis missingrequires_cftime. - 3: datatree tests assume netCDF4 is installed (
NameError: name 'nc4' is not definedin a fixture, andtest_default_write_engine).
Only 4 failures depend on the GIL: test_open_mfdataset_manyfiles[scipy-20-*-*-5] (file_cache_maxsize=5, parallel dask reads). CachingFileManager evicts and closes a scipy file opened with mmap while another thread still uses its data. The resulting RuntimeWarning leaves the LRU cache inconsistent and ends in a KeyError. These pass with PYTHON_GIL=1.
Upstream status
Python 3.15 (checked when there are builds on conda-forge and wheels on PyPI):
- numpy: 2.5.4 on conda-forge and PyPI
- numba: 0.68.0 on conda-forge and PyPI (numba/numba#10581)
- dask: pure Python (on conda-forge use
dask-core; thedaskmetapackage needs pyarrow) - netCDF4:
abi3builds of 1.7.4 on conda-forge and PyPI - h5netcdf: pure Python
- bottleneck: 1.6.0 on conda-forge; PyPI wheels need a release (support merged in pydata/bottleneck#589, release requested in pydata/bottleneck#591)
Check when: a bottleneck release after 1.6.0 shipscp315wheels on PyPI. - cftime: 1.6.5 on conda-forge,
abi3wheels of 1.6.6 on PyPI - numcodecs: 0.17.0 on conda-forge; no PyPI wheels: zarr-developers/numcodecs#874 (zarr-developers/numcodecs#842 was closed without merging)
Check when: a numcodecs release shipscp315wheels on PyPI (0.17.0 doesn't). - pyarrow: wheels of 26.0.0 on PyPI;
py315builds of 25.0.0 on conda-forge (conda-forge/pyarrow-feedstock#184) - h5py: 3.16.0 on conda-forge; no PyPI wheels: h5py/h5py#2972 (closed;
abi3wheels from h5py/h5py#2885 are not released yet)
Check when: an h5py release shipscp315orabi3wheels on PyPI (3.16.0 has neither). - numexpr: 2.14.2 on conda-forge; no PyPI wheels: pydata/numexpr#579
Check when: a numexpr release shipscp315wheels on PyPI (2.14.2 doesn't). - cf-units (needed by iris):
abi3builds of 3.3.1 on conda-forge and PyPI - pyyaml (needed by dask): 6.0.3 on conda-forge; no PyPI wheels: yaml/pyyaml#951
Check when: a pyyaml release shipscp315wheels on PyPI (6.0.3 doesn't).
Free-threaded Python 3.15t (checked when there are cp315t wheels on PyPI):
- conda-forge builds: the py315 migration started in conda-forge/conda-forge-pinning-feedstock#8911, but the free-threading migration only covers 3.14t so far
Check when: conda-forge starts apython315tmigration and numpy/pandas/scipy havecp315tbuilds. - numpy:
cp315twheels of 2.5.4 - numba (also needed by numbagg): numba/numba#10473 (free-threading in general); 3.15t support is announced for the next release in numba/numba#10581
Check when: a numba release shipscp315twheels on PyPI (0.68.0 only hascp315). - dask: pure Python
- netCDF4:
cp315twheels of 1.7.5 (Unidata/netcdf4-python#1509) - h5netcdf: pure Python (but needs h5py, see below)
- bottleneck: release requested in pydata/bottleneck#591 (see also pydata/bottleneck#532 on free-threading safety)
Check when: a bottleneck release shipscp315twheels on PyPI. - cftime (also needed by nc-time-axis and iris):
cp315twheels of 1.6.6.1 (Unidata/cftime#421, Unidata/cftime#424) - numcodecs (also needed by zarr): zarr-developers/numcodecs#874 (see also zarr-developers/numcodecs#749 for free-threading in general; 3.14t support in zarr-developers/numcodecs#858)
Check when: a numcodecs release shipscp315twheels on PyPI (0.17.0 doesn't). - pyarrow:
cp315twheels of 26.0.0 - h5py: h5py/h5py#2475 (free-threading support;
abi3twheels planned, see h5py/h5py#2972)
Check when: an h5py release shipscp315torabi3twheels on PyPI. - numexpr: pydata/numexpr#579 (2.14.2 already has
cp314twheels, so the next release will likely includecp315t)
Check when: a numexpr release shipscp315twheels on PyPI. - cf-units (needed by iris): no issue yet; 3.3.1 only has
abi3wheels
Check when: a cf-units release shipscp315torabi3twheels on PyPI. - pyyaml (needed by dask): yaml/pyyaml#951 (6.0.3 already has
cp314twheels; see also yaml/pyyaml#870 for free-threading in general)
Check when: a pyyaml release shipscp315twheels on PyPI.
Other test dependencies without 3.15t wheels on PyPI (checked 2026-10-13): psutil and tornado (distributed), google-crc32c (zarr) and lz4 (dask extras). psutil, tornado and lz4 build from source on 3.15t; google-crc32c builds but falls back to a pure Python implementation with a RuntimeWarning on import. cf-units doesn't build without udunits2, so iris has to be left out of the 3.15t env.
Proposal for CI
- Add
test-py315alongside the 3.14 envs, and only replace 3.14 once pyarrow has 3.15 builds on conda-forge. Until then, move pyarrow from theaccelfeature into its own feature and usedask-corein the 3.15 env. - Add
test-py315t(ubuntu only) with a condapython-freethreadinginterpreter and PyPI wheels, without h5netcdf until h5py hascp315twheels. - Fix the test guards and
ensure_warningsabove, and look into the file manager race.
[This is Claude Code on behalf of Michael Niklas]
- Dominant language
- Python
- Stars
- 4.2k
- Forks
- 1.5k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 74
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pydata/xarray
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
`DataTree.map_over_datasets` behavior can be obscure sometimesPossibly taken @mohansree14 claimed this 23 days ago. Openneeds triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pydata/xarray#11813 · 1 comment ·
Maintainers usually reply within 1 day
-
Comparing attrs that contain a dict of NumPy arrays raises ValueError in identical / assert_identicalPossibly taken @SohamXYZDev claimed this 29 days ago. Openbug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
pydata/xarray#11777 · 1 comment ·
Maintainers usually reply within 1 day
-
RangeIndex` with datetime64 bounds cannot be printed (`Unknown format code 'g'`)Possibly taken @d-chambers claimed this 60 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pydata/xarray#11598 · 3 comments ·
Maintainers usually reply within 1 day
-
DataTree constructor error message says dict even though dict is not acceptedPossibly taken @aryansk claimed this 100 days ago. Openbug contrib-good-first-issue topic-DataTree topic-error reporting
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pydata/xarray#11514 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
tests
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[Plugin] 群聊记忆 · 人格养成Open
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
-
bug maintainer-managed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
awslabs/visual-asset-management-system#1759 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100