tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of cmdstanpy and StatsBase.jl — release velocity, themes, recent moves, and the top alternatives to consider.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
CmdStanPy is at v1.3.0, which added a diagnose method on CmdStanModel, sampler timing information, create_inits() across the stanfit classes, and much faster MCMC CSV parsing. Every release in this window opens with the same notice: the next non-bugfix release will be 2.0 and will remove existing deprecations. In line with that, 1.3.0 drops Python 3.8 and renames the metric argument to inv_metric.
StatsBase.jl is in caretaker mode — correctness fixes in, dependency bumps out.
StatsBase.jl is deep in the 0.34 patch series, releasing every few months with changes that are either small correctness fixes or bot-authored dependency bumps. The most substantive recent release, 0.34.10, fixed weighted sampling with UnitWeights, sped up unweighted ecdf, and widened quantile to accept non-Real element types. Since then the tags have thinned to CI action bumps and a diff-only note.
CmdStanPy is at v1.3.0, which added a diagnose method on CmdStanModel, sampler timing information, create_inits() across the stanfit classes, and much faster MCMC CSV parsing. Every release in this window opens with the same notice: the next non-bugfix release will be 2.0 and will remove existing deprecations. In line with that, 1.3.0 drops Python 3.8 and renames the metric argument to inv_metric.
The package tracks upstream Stan and prepares for its own break. New inference methods arrive as Stan ships them — Laplace with Stan 2.32, Pathfinder with 2.33 — while the interface work is mostly deprecation staging and CSV input-output performance. The repeated 2.0 warning across two years of releases suggests the cut has been deferred more than once.
The notice at the top of every release points to 2.0 as the next non-bugfix version, removing the deprecations staged here including the metric argument.
StatsBase.jl is deep in the 0.34 patch series, releasing every few months with changes that are either small correctness fixes or bot-authored dependency bumps. The most substantive recent release, 0.34.10, fixed weighted sampling with UnitWeights, sped up unweighted ecdf, and widened quantile to accept non-Real element types. Since then the tags have thinned to CI action bumps and a diff-only note.
This is the shape of a foundational Julia package that has reached its intended scope: the API is settled, and maintenance means keeping compat bounds current and closing long-tail correctness issues raised by users. Nothing in the feed suggests new statistical capability is being staged. The most likely reason is that new work now lands in the downstream packages that build on StatsBase rather than in StatsBase itself.
Expect more 0.34.x patches on the same rhythm — CompatHelper bumps and occasional user-reported edge-case fixes — with no signal in these entries that a 0.35 or 1.0 is being prepared.
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 cmdstanpy or StatsBase.jl.
tidyr replaced separate() with a family that says what it does.
modeltime built conformal intervals in, then went quiet on features.
performance keeps adding ways to check a model you have already fitted.
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 cmdstanpy alternatives → · See all StatsBase.jl alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. cmdstanpy and StatsBase.jl 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. cmdstanpy and StatsBase.jl 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 cmdstanpy alternatives in Analytics are ranked by recent ship velocity. Browse the "cmdstanpy alternatives" section above for the current picks, or visit /alternatives/cmdstanpy for the full list with editorial commentary on each.
Top StatsBase.jl alternatives in Analytics are ranked by recent ship velocity. Browse the "StatsBase.jl alternatives" section above for the current picks, or visit /alternatives/statsbase-jl for the full list with editorial commentary on each.