tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of cmdstanpy and PySCF — 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.
Quantum chemistry package adding whole method families every release.
PySCF is a Python-based quantum chemistry toolkit, and its release cadence is unusually feature-dense: each version lands multiple new electronic-structure methods rather than polishing existing ones. Recent releases have built out the GW/BSE excited-state stack, k-point RPA for periodic systems, higher-order coupled cluster, and multi-state PDFT with analytical gradients. Platform work runs alongside — Windows DLL compatibility, GPU4PySCF interfacing, and configurable einsum backends.
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.
PySCF is a Python-based quantum chemistry toolkit, and its release cadence is unusually feature-dense: each version lands multiple new electronic-structure methods rather than polishing existing ones. Recent releases have built out the GW/BSE excited-state stack, k-point RPA for periodic systems, higher-order coupled cluster, and multi-state PDFT with analytical gradients. Platform work runs alongside — Windows DLL compatibility, GPU4PySCF interfacing, and configurable einsum backends.
Two arcs are visible. The methods arc is pushing toward periodic (PBC) parity with molecular calculations — PBC GW, PBC RPA, SOC-ECP for PBC DFT, QM/MM for periodic systems all landed in this window. The infrastructure arc is about getting PySCF to run where it previously did not: Windows, GPUs, alternative tensor-contraction backends.
The PBC catch-up should continue, since each release closes another gap between molecular and periodic implementations of the same method; the entries do not indicate which gap is next.
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 PySCF.
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 PySCF alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. PySCF is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. PySCF is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 PySCF alternatives in Analytics are ranked by recent ship velocity. Browse the "PySCF alternatives" section above for the current picks, or visit /alternatives/pyscf for the full list with editorial commentary on each.