tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of cmdstanpy and Simple Analytics — 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.
Privacy analytics tightening its API and moving IP blocking off the CDN
The feed stores each change several times — once with the body text captured as the title, once as a clean headline, sometimes a third time with a date prefix. Behind the duplication, three real changes: API v6 with proper interval support while v5 stays unchanged for compatibility, IP blocking moved off the bunny.net CDN so it works on custom domains and applies per site rather than account-wide, and Events Explorer readability work with column truncation, a full-width toggle and collapsible headers.
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.
The feed stores each change several times — once with the body text captured as the title, once as a clean headline, sometimes a third time with a date prefix. Behind the duplication, three real changes: API v6 with proper interval support while v5 stays unchanged for compatibility, IP blocking moved off the bunny.net CDN so it works on custom domains and applies per site rather than account-wide, and Events Explorer readability work with column truncation, a full-width toggle and collapsible headers.
The work is about removing borrowed constraints. IP blocking inherited the CDN's limits and blast radius; moving it in-house made it per-site and custom-domain compatible. API v6 does the same for time handling — hourly data separates day and hour, weeks and months carry explicit start dates — while keeping v5 stable so nobody is forced to migrate. Both are the moves of a product whose users integrate it and stay.
With v6 shipped alongside an unchanged v5, expect a deprecation timeline for v5 to be the next API announcement, though the entries do not name one.
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 Simple Analytics.
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 Simple Analytics 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 Simple Analytics 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 Simple Analytics 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 Simple Analytics alternatives in Analytics are ranked by recent ship velocity. Browse the "Simple Analytics alternatives" section above for the current picks, or visit /alternatives/simple-analytics for the full list with editorial commentary on each.