`hats-import` version resolves to 0.5.1

[hombit]

Bug report

hats-import version may be resolved to a pretty old version due to a Dask version pin we use. I've faced this issue when working on https://github.com/UniverseTBD/mmu-hdf-to-hats, see pyproject.toml there. I guess it happens because of the dask version pin we have.

An example:

uv pip install --dry-run 'dask[distributed,diagnostics]' hats-import
Using Python 3.14.0 environment at: .virtualenvs/tmp-test
Resolved 63 packages in 235ms
Would install 63 packages
 + aiohappyeyeballs==2.6.1
 + aiohttp==3.13.2
 + aiosignal==1.4.0
 + annotated-types==0.7.0
 + astropy==7.2.0
 + astropy-iers-data==0.2025.12.22.0.40.30
 + attrs==25.4.0
 + bokeh==3.8.1
 + cdshealpix==0.7.2
 + click==8.3.1
 + cloudpickle==3.1.2
 + contourpy==1.3.3
 + dask==2025.12.0
 + deprecated==1.3.1
 + distributed==2025.12.0
 + frozenlist==1.8.0
 + fsspec==2025.12.0
 + hats==0.7.3
 + hats-import==0.5.1
 + idna==3.11
 + jinja2==3.1.6
 + jproperties==2.1.2
 + llvmlite==0.46.0
 + locket==1.0.0
 + lz4==4.4.5
 + markupsafe==3.0.3
 + mocpy==0.19.1
 + msgpack==1.1.2
 + multidict==6.7.0
 + narwhals==2.14.0
 + nested-pandas==0.6.4
 + numba==0.63.1
 + numpy==2.3.5
 + packaging==25.0
 + pandas==2.3.3
 + partd==1.4.2
 + pathlib-abc==0.5.2
 + pillow==12.0.0
 + propcache==0.4.1
 + psutil==7.1.3
 + pyarrow==22.0.0
 + pydantic==2.12.5
 + pydantic-core==2.41.5
 + pyerfa==2.0.1.5
 + python-dateutil==2.9.0.post0
 + pytz==2025.2
 + pyyaml==6.0.3
 + scipy==1.16.3
 + six==1.17.0
 + sortedcontainers==2.4.0
 + tblib==3.2.2
 + toolz==1.1.0
 + tornado==6.5.4
 + tqdm==4.67.1
 + typing-extensions==4.15.0
 + typing-inspection==0.4.2
 + tzdata==2025.3
 + universal-pathlib==0.3.7
 + urllib3==2.6.2
 + wrapt==2.0.1
 + xyzservices==2025.11.0
 + yarl==1.22.0
 + zict==3.0.0

Workaround is pinning hats-import to a more recent version, e.g. uv pip install --dry-run 'dask[distributed,diagnostics]' 'hats-import>=0.7.3'

Environment Information

Before submitting
Please check the following:

• I have described the situation in which the bug arose, including what code was executed, and any applicable data others will need to reproduce the problem.
• I have included information about my environment, including the version of this package (e.g. hats_import.__version__)
• I have included available evidence of the unexpected behavior (including error messages, screenshots, and/or plots) as well as a description of what I expected instead.
• If I have a solution in mind, I have provided an explanation and/or pseudocode and/or task list.

[delucchi-cmu]

@hombit I suspect that this is resolved in v0.8, with https://github.com/astronomy-commons/hats-import/pull/662/files

Can you try to reproduce?

[hombit]

Yes, I still can reproduce it, it would still install hats-import 0.5.1 on Python 3.11. It works fine (selects hats-import 0.8.0) on Python 3.12-3.14. Tested on macOS.

[delucchi-cmu]

Well, yes, we still have the pin for python 3.11... There's some weird behavior with dask expressions and python 3.11 that I was kind of hoping to ignore with a version pin until 3.11 is end-of-life.

[nevencaplar]

Can we pinpoint what the issue is and bring it up during next DASK community meeting?