r/madeinpython • u/Emergency-Tutor-7 • 1h ago
The NumPy build of my scientific computing library: same API as the pure-Python one, compiled speed
Repo: https://github.com/Furox-Art/scientific-computing-system-2.0 - PyPI scientific-computing-system-2.0 5.5.0, import name cds2, console script cds2.
This is the second half of a pair. scientific-computing-system is pure Python with zero runtime dependencies; this one is the NumPy/SciPy/pandas/matplotlib build of the same project. Same API, so a script can move between them.
It covers the usual ground - linear algebra, statistics, optimization, signal processing, information theory, chaos, Bayesian helpers, metaheuristics, geometry, reinforcement learning - with the compiled backends doing the heavy arithmetic.
Two naming things, because they confuse people every time: "2.0" names the generation of the project, not the release number. The current release is 5.5.0 and PyPI has never published a 2.x version. There was no clever reason for that, it is just how the version line went.
One honest limit: it is not a thin wrapper around SciPy with friendlier names. Where a compiled backend does not cover something, the pure-Python implementation from the other repo is what runs, and it is slow. The repo says which is which per module instead of pretending the speed is uniform.