modeltime
modeltime built conformal intervals in, then went quiet on features.
A side-by-side editorial comparison of PySCF and tidyr — release velocity, themes, recent moves, and the top alternatives to consider.
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.
tidyr replaced separate() with a family that says what it does.
tidyr is at 1.3.2, a collection of argument additions — fill() gains .by, expand_grid() gains .vary — and better error messages around unchop() and pivot_wider_spec(). The structural work is 1.3.0, which introduced separate_wider_delim(), separate_wider_position(), separate_wider_regex(), separate_longer_delim() and separate_longer_position() as thorough replacements for separate(), extract() and separate_rows().
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.
tidyr is at 1.3.2, a collection of argument additions — fill() gains .by, expand_grid() gains .vary — and better error messages around unchop() and pivot_wider_spec(). The structural work is 1.3.0, which introduced separate_wider_delim(), separate_wider_position(), separate_wider_regex(), separate_longer_delim() and separate_longer_position() as thorough replacements for separate(), extract() and separate_rows().
Two habits define this window. Verbs are being split into explicitly named variants rather than overloaded with arguments, which is what the separate_* family does to separate(). And .by is spreading as the standard way to express grouping inline — nest(.by=) in 1.3.0, fill(.by=) in 1.3.2 — pulling users away from wrapping calls in group_by().
Given that .by has now reached fill() and nest(), the next release most likely extends the same argument to further verbs rather than reworking another function family.
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 PySCF or tidyr.
modeltime built conformal intervals in, then went quiet on features.
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.
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 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.
Top tidyr alternatives in Analytics are ranked by recent ship velocity. Browse the "tidyr alternatives" section above for the current picks, or visit /alternatives/tidyr for the full list with editorial commentary on each.