tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of modeltime and statsmodels — release velocity, themes, recent moves, and the top alternatives to consider.
modeltime built conformal intervals in, then went quiet on features.
modeltime is at 1.3.3, a single change making the package robust to xgboost version shifts. The feature weight sits in 1.3.2, which added a future-based parallel backend, the maape() accuracy metric and dials helpers for ADAM engine tuning, and further back in the 1.2.8 and 1.3.0 pair that introduced conformal prediction intervals and then carried them through the nested forecasting workflow.
statsmodels ships only what the ecosystem breaks — six releases, no new statistics.
Every release in this window is a compatibility release. 0.14.2 and 0.14.3 absorbed NumPy 2, 0.14.5 fixed an import failure caused by SciPy 1.16, and 0.14.6 did the same for pandas 3.0. The only additive change across two years is Pyodide support in 0.14.4, described in its own notes as one feature and no fixes. A 0.15.0.dev0 tag exists from 2023 and has not been followed by a 0.15 release.
modeltime is at 1.3.3, a single change making the package robust to xgboost version shifts. The feature weight sits in 1.3.2, which added a future-based parallel backend, the maape() accuracy metric and dials helpers for ADAM engine tuning, and further back in the 1.2.8 and 1.3.0 pair that introduced conformal prediction intervals and then carried them through the nested forecasting workflow.
The arc runs from uncertainty quantification to execution. Conformal intervals arrived first and were then threaded through nested fitting, refitting and the printed forecast tables so users can see which confidence method produced an interval. The later work moves down a layer to how forecasts are computed — a portable future backend replacing foreach tuning — rather than what they express.
With only an xgboost compatibility fix since the 1.3.2 feature release, the entries do not support a confident prediction about what comes next beyond continued dependency maintenance.
Every release in this window is a compatibility release. 0.14.2 and 0.14.3 absorbed NumPy 2, 0.14.5 fixed an import failure caused by SciPy 1.16, and 0.14.6 did the same for pandas 3.0. The only additive change across two years is Pyodide support in 0.14.4, described in its own notes as one feature and no fixes. A 0.15.0.dev0 tag exists from 2023 and has not been followed by a 0.15 release.
The library is being kept alive rather than developed: each release answers a break introduced upstream, and the interval between them is set by the NumPy, SciPy and pandas release calendars rather than by anything statsmodels is building. Two consecutive releases whose stated purpose was restoring the ability to import the package is the sharpest available signal about maintainer bandwidth. The 0.15 line remains a dev tag with no visible progress toward a release.
The next release is most likely another compatibility patch triggered by a NumPy, SciPy or pandas major, and nothing in these entries indicates 0.15 is close.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either modeltime or statsmodels.
tidyr replaced separate() with a family that says what it does.
performance keeps adding ways to check a model you have already fitted.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
See all modeltime alternatives → · See all statsmodels alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. modeltime and statsmodels are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. modeltime and statsmodels are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top modeltime alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime alternatives" section above for the current picks, or visit /alternatives/modeltime for the full list with editorial commentary on each.
Top statsmodels alternatives in Analytics are ranked by recent ship velocity. Browse the "statsmodels alternatives" section above for the current picks, or visit /alternatives/statsmodels for the full list with editorial commentary on each.