Congrats to releasing TiRex-2 and the performance improvements 🚀
We would like to integrate TiRex-2 into Darts, similar to how we already integrated the original TiRex via tirex-ts. Looking at dependency constraints in tirex-2 they are significantly tighter than those in tirex-ts, which makes the integration challenging.
The current tirex-2 v0.1.1 pins dependencies quite aggressively using compatible-release (~=) constraints. Here are some examples:
| Dependency |
tirex-2 constraint |
tirex-ts (v1) |
Darts constraint |
| Python |
>=3.11, <3.14 |
>=3.10 |
>=3.10 |
numpy |
~=2.1.3 (i.e. >=2.1.3, <2.2) |
— |
>=1.26.0 |
torch |
>=2.8, <2.10 |
— |
>=2.0.0 |
huggingface-hub |
~=0.32.0 (i.e. >=0.32.0, <0.33) |
— |
>=0.35.3 |
Would it be possible to relax the constraints to use lower-bound-only pins, similar to how tirex-ts handles it?
Congrats to releasing TiRex-2 and the performance improvements 🚀
We would like to integrate TiRex-2 into Darts, similar to how we already integrated the original TiRex via
tirex-ts. Looking at dependency constraints intirex-2they are significantly tighter than those intirex-ts, which makes the integration challenging.The current
tirex-2v0.1.1 pins dependencies quite aggressively using compatible-release (~=) constraints. Here are some examples:tirex-2constrainttirex-ts(v1)>=3.11, <3.14>=3.10>=3.10numpy~=2.1.3(i.e.>=2.1.3, <2.2)>=1.26.0torch>=2.8, <2.10>=2.0.0huggingface-hub~=0.32.0(i.e.>=0.32.0, <0.33)>=0.35.3Would it be possible to relax the constraints to use lower-bound-only pins, similar to how
tirex-tshandles it?