hictkpy builds without problems on Python 3.13, and given that we do not link to any external libraries at runtime, we could in principle build wheels for Python 3.13 and let users deal with third-party deps that do not have wheels for Python 3.13 (currently pyarrow).
However, in the remote case where pyarrow==18 public Python API changes in a way that breaks hictkpy, we would be left with a version of hictkpy that installs fine, but fails at runtime when using Python 3.13.
Thus, I think it is better to err on the safe side and ship hictkpy v1.0.0 without wheels for Python 3.13.
Then, release v1.0.1 at a later stage, when pyarrow==18 becomes available, with pre-built Python 3.13 wheels.
Partial progress towards solving https://github.com/paulsengroup/hictkpy/issues/84.
hictkpy builds without problems on Python 3.13, and given that we do not link to any external libraries at runtime, we could in principle build wheels for Python 3.13 and let users deal with third-party deps that do not have wheels for Python 3.13 (currently pyarrow).
However, in the remote case where pyarrow==18 public Python API changes in a way that breaks hictkpy, we would be left with a version of hictkpy that installs fine, but fails at runtime when using Python 3.13.
Thus, I think it is better to err on the safe side and ship hictkpy v1.0.0 without wheels for Python 3.13. Then, release v1.0.1 at a later stage, when pyarrow==18 becomes available, with pre-built Python 3.13 wheels.