scientific-computing-system 2.0.0__tar.gz → 2.0.1__tar.gz

{scientific_computing_system-2.0.0 → scientific_computing_system-2.0.1}/CHANGELOG.md

@@ -7,6 +7,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [v2.0.1] - 2026-09-29
+
+Metadata-only patch release for improved PyPI discoverability. No runtime API or numerical behavior changes.
+
+### Changed
+
+- Expanded PyPI keywords and classifiers for reproducibility, uncertainty quantification, sensitivity analysis, dimensional analysis, scientific workflows, ODE/PDE, and related scientific-computing searches.
+- Refreshed development lock versions required by the current security audit.
+- Normalized repository trailing whitespace required by pre-commit.
+
+
 ### Added
 
 - **Random Forest classifier** (`cds.ml`): bagged CART trees with

{scientific_computing_system-2.0.0 → scientific_computing_system-2.0.1}/CITATION.cff

@@ -2,7 +2,7 @@ cff-version: 1.2.0
 message: "If you use this software, please cite it using the metadata from this file."
 type: software
 title: "scientific-computing-system"
-version: 1.7.0
+version: 2.0.1
 authors:
   - name: "Furox-Art"
     email: "furkanarkn1451@gmail.com"
@@ -10,7 +10,7 @@ abstract: "Pure Python computational science system — quantum simulation, sign
 license: MIT
 repository-code: "https://github.com/Furox-Art/scientific-computing-system"
 url: "https://github.com/Furox-Art/scientific-computing-system"
-date-released: "2026-08-24"
+date-released: "2026-09-29"
 keywords:
   - "pure python"
   - "scientific computing"
@@ -25,5 +25,5 @@ preferred-citation:
   authors:
     - name: "Furox-Art"
   year: 2026
-  version: 1.7.0
+  version: 2.0.1
   url: "https://github.com/Furox-Art/scientific-computing-system"

scientific_computing_system-2.0.1/PKG-INFO

@@ -0,0 +1,139 @@
+Metadata-Version: 2.5
+Name: scientific-computing-system
+Version: 2.0.1
+Summary: A pure-Python computational science platform for numerical methods, modeling, validation, uncertainty, scientific workflows, dimensional analysis, and optional research-data backends. Zero runtime dependencies.
+Project-URL: Homepage, https://github.com/Furox-Art/scientific-computing-system
+Project-URL: Repository, https://github.com/Furox-Art/scientific-computing-system
+Project-URL: Documentation, https://furox-art.github.io/scientific-computing-system/
+Project-URL: PyPI, https://pypi.org/project/scientific-computing-system/
+Project-URL: Issues, https://github.com/Furox-Art/scientific-computing-system/issues
+Project-URL: Changelog, https://github.com/Furox-Art/scientific-computing-system/releases
+Author-email: Furox-Art <furkanarkn1451@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: data-analysis,differential-equations,dimensional-analysis,graph-theory,hypothesis-generation,knowledge-graph,linear-algebra,machine-learning,monte-carlo,nlp,numerical-integration,numerical-methods,ode,optimization,pde,physics,probability,pure-python,quantum,reproducibility,scientific-computing,scientific-workflows,sensitivity-analysis,signal-processing,statistics,symbolic-math,uncertainty-quantification
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Scientific/Engineering :: Mathematics
+Classifier: Topic :: Scientific/Engineering :: Physics
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Provides-Extra: all
+Requires-Dist: build; extra == 'all'
+Requires-Dist: h5py>=3.10; extra == 'all'
+Requires-Dist: hypothesis>=6.100; extra == 'all'
+Requires-Dist: ipykernel; extra == 'all'
+Requires-Dist: matplotlib>=3.8.0; extra == 'all'
+Requires-Dist: mkdocs-material>=9.0.0; extra == 'all'
+Requires-Dist: mkdocs>=1.5.0; extra == 'all'
+Requires-Dist: mkdocstrings[python]>=0.24.0; extra == 'all'
+Requires-Dist: mypy>=1.10; extra == 'all'
+Requires-Dist: netcdf4>=1.6; extra == 'all'
+Requires-Dist: notebook; extra == 'all'
+Requires-Dist: numpy>=1.26; extra == 'all'
+Requires-Dist: pandas>=2.0; extra == 'all'
+Requires-Dist: pre-commit; extra == 'all'
+Requires-Dist: pytest-cov; extra == 'all'
+Requires-Dist: pytest>=8.0; extra == 'all'
+Requires-Dist: ruff>=0.4; extra == 'all'
+Requires-Dist: scikit-learn>=1.4; extra == 'all'
+Requires-Dist: scipy>=1.11; extra == 'all'
+Requires-Dist: statsmodels>=0.14; extra == 'all'
+Requires-Dist: streamlit>=1.30.0; extra == 'all'
+Requires-Dist: sympy>=1.12; extra == 'all'
+Requires-Dist: z3-solver>=4.12.2; extra == 'all'
+Provides-Extra: dashboard
+Requires-Dist: pandas; extra == 'dashboard'
+Requires-Dist: streamlit>=1.30.0; extra == 'dashboard'
+Provides-Extra: dev
+Requires-Dist: build; extra == 'dev'
+Requires-Dist: ipykernel; extra == 'dev'
+Requires-Dist: mypy>=1.10; extra == 'dev'
+Requires-Dist: notebook; extra == 'dev'
+Requires-Dist: numpy<2.5,>=2.0; extra == 'dev'
+Requires-Dist: pandas-stubs>=2.0; extra == 'dev'
+Requires-Dist: pre-commit; extra == 'dev'
+Requires-Dist: ruff>=0.4; extra == 'dev'
+Provides-Extra: docs
+Requires-Dist: mkdocs-material>=9.0.0; extra == 'docs'
+Requires-Dist: mkdocs>=1.5.0; extra == 'docs'
+Requires-Dist: mkdocstrings[python]>=0.24.0; extra == 'docs'
+Provides-Extra: io
+Requires-Dist: h5py>=3.10; extra == 'io'
+Requires-Dist: netcdf4>=1.6; extra == 'io'
+Provides-Extra: pandas
+Requires-Dist: pandas>=2.0; extra == 'pandas'
+Provides-Extra: plot
+Requires-Dist: matplotlib>=3.8.0; extra == 'plot'
+Provides-Extra: promo
+Requires-Dist: imageio-ffmpeg>=0.5.1; extra == 'promo'
+Requires-Dist: matplotlib>=3.8.0; extra == 'promo'
+Requires-Dist: numpy>=1.26.0; extra == 'promo'
+Requires-Dist: pillow>=10.0.0; extra == 'promo'
+Provides-Extra: property
+Requires-Dist: hypothesis>=6.100; extra == 'property'
+Provides-Extra: scientific
+Requires-Dist: numpy>=1.26; extra == 'scientific'
+Requires-Dist: scikit-learn>=1.4; extra == 'scientific'
+Requires-Dist: scipy>=1.11; extra == 'scientific'
+Requires-Dist: statsmodels>=0.14; extra == 'scientific'
+Requires-Dist: sympy>=1.12; extra == 'scientific'
+Requires-Dist: z3-solver>=4.12.2; extra == 'scientific'
+Provides-Extra: test
+Requires-Dist: pytest-cov; extra == 'test'
+Requires-Dist: pytest>=8.0; extra == 'test'
+Description-Content-Type: text/markdown
+
+<p align="center">
+  <img src="assets/logo.svg" alt="scientific-computing-system" width="640">
+</p>
+
+<h1 align="center">scientific-computing-system</h1>
+
+<p align="center"><b>A pure-Python computational science platform for numerical methods, modeling, validation, uncertainty, scientific workflows, dimensional analysis, and reproducible research.</b></p>
+
+<p align="center">
+  <a href="https://pypi.org/project/scientific-computing-system/"><img src="https://img.shields.io/pypi/v/scientific-computing-system.svg" alt="PyPI version"></a>
+  <a href="https://www.npmjs.com/package/scientific-computing-system"><img src="https://img.shields.io/npm/v/scientific-computing-system.svg" alt="npm version"></a>
+  <a href="https://pypi.org/project/scientific-computing-system/"><img src="https://img.shields.io/pypi/dm/scientific-computing-system.svg" alt="PyPI downloads"></a>
+  <a href="https://www.python.org/downloads/"><img src="https://img.shields.io/badge/python-3.10+-green.svg" alt="Python 3.10+"></a>
+  <a href="https://codecov.io/gh/Furox-Art/scientific-computing-system"><img src="https://codecov.io/gh/Furox-Art/scientific-computing-system/branch/main/graph/badge.svg" alt="codecov"></a>
+  <a href="https://github.com/Furox-Art/scientific-computing-system/actions/workflows/tests.yml"><img src="https://github.com/Furox-Art/scientific-computing-system/actions/workflows/tests.yml/badge.svg" alt="CI"></a>
+  <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue.svg" alt="License: MIT"></a>
+  <a href="https://furox-art.github.io/scientific-computing-system/"><img src="https://img.shields.io/badge/docs-mkdocs-teal.svg" alt="Docs"></a>
+  <a href="https://github.com/Furox-Art/scientific-computing-system/releases"><img src="https://img.shields.io/github/v/release/Furox-Art/scientific-computing-system.svg" alt="GitHub release"></a>
+</p>
+
+I wrote this because NumPy and SciPy are incredible, but they're also 20 years old and carry two decades of design decisions that don't always make sense anymore.
+
+This is a from-scratch rethinking of what scientific computing in Python could look like if we started today. No C extensions, no Fortran legacy, no dependency hell. Just Python, type hints, and algorithms that are actually readable.
+
+## What's inside
+
+- **Linear algebra**: SVD, QR, Cholesky, eigenvalues-all implemented in pure Python with proper error handling
+- **Optimization**: gradient descent, constrained optimization, metaheuristics
+- **Statistics**: hypothesis testing, Bayesian inference, time series
+- **Machine learning**: PCA, clustering, simple neural nets (educational, not production)
+- **Quantum computing**: circuit simulation, state vectors, basic gates
+- **Signal processing**: filters, wavelets, STFT
+- **ODE/PDE solvers**: stiff and non-stiff, symplectic integrators
+
+## The catch
+
+It's slower than NumPy. Sometimes 10x slower, sometimes 100x. That's the price of pure Python. But it's also completely transparent-you can read every algorithm, understand every step, and modify anything without compiling C.
+
+I use it for prototyping, for teaching, and for cases where I need to know exactly what the computer is doing. For production number crunching, I still reach for NumPy.
+
+## License
+
+MIT.

scientific_computing_system-2.0.1/README.md

@@ -0,0 +1,43 @@
+<p align="center">
+  <img src="assets/logo.svg" alt="scientific-computing-system" width="640">
+</p>
+
+<h1 align="center">scientific-computing-system</h1>
+
+<p align="center"><b>A pure-Python computational science platform for numerical methods, modeling, validation, uncertainty, scientific workflows, dimensional analysis, and reproducible research.</b></p>
+
+<p align="center">
+  <a href="https://pypi.org/project/scientific-computing-system/"><img src="https://img.shields.io/pypi/v/scientific-computing-system.svg" alt="PyPI version"></a>
+  <a href="https://www.npmjs.com/package/scientific-computing-system"><img src="https://img.shields.io/npm/v/scientific-computing-system.svg" alt="npm version"></a>
+  <a href="https://pypi.org/project/scientific-computing-system/"><img src="https://img.shields.io/pypi/dm/scientific-computing-system.svg" alt="PyPI downloads"></a>
+  <a href="https://www.python.org/downloads/"><img src="https://img.shields.io/badge/python-3.10+-green.svg" alt="Python 3.10+"></a>
+  <a href="https://codecov.io/gh/Furox-Art/scientific-computing-system"><img src="https://codecov.io/gh/Furox-Art/scientific-computing-system/branch/main/graph/badge.svg" alt="codecov"></a>
+  <a href="https://github.com/Furox-Art/scientific-computing-system/actions/workflows/tests.yml"><img src="https://github.com/Furox-Art/scientific-computing-system/actions/workflows/tests.yml/badge.svg" alt="CI"></a>
+  <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue.svg" alt="License: MIT"></a>
+  <a href="https://furox-art.github.io/scientific-computing-system/"><img src="https://img.shields.io/badge/docs-mkdocs-teal.svg" alt="Docs"></a>
+  <a href="https://github.com/Furox-Art/scientific-computing-system/releases"><img src="https://img.shields.io/github/v/release/Furox-Art/scientific-computing-system.svg" alt="GitHub release"></a>
+</p>
+
+I wrote this because NumPy and SciPy are incredible, but they're also 20 years old and carry two decades of design decisions that don't always make sense anymore.
+
+This is a from-scratch rethinking of what scientific computing in Python could look like if we started today. No C extensions, no Fortran legacy, no dependency hell. Just Python, type hints, and algorithms that are actually readable.
+
+## What's inside
+
+- **Linear algebra**: SVD, QR, Cholesky, eigenvalues-all implemented in pure Python with proper error handling
+- **Optimization**: gradient descent, constrained optimization, metaheuristics
+- **Statistics**: hypothesis testing, Bayesian inference, time series
+- **Machine learning**: PCA, clustering, simple neural nets (educational, not production)
+- **Quantum computing**: circuit simulation, state vectors, basic gates
+- **Signal processing**: filters, wavelets, STFT
+- **ODE/PDE solvers**: stiff and non-stiff, symplectic integrators
+
+## The catch
+
+It's slower than NumPy. Sometimes 10x slower, sometimes 100x. That's the price of pure Python. But it's also completely transparent-you can read every algorithm, understand every step, and modify anything without compiling C.
+
+I use it for prototyping, for teaching, and for cases where I need to know exactly what the computer is doing. For production number crunching, I still reach for NumPy.
+
+## License
+
+MIT.

scientific_computing_system-2.0.1/SECURITY.md

@@ -0,0 +1,82 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported | Notes |
+|---|---|---|
+| 2.0.x | Yes | Current stable release line |
+| < 2.0 | No | Superseded by the 2.0 release line unless a specific security advisory states otherwise |
+
+Security fixes target the current stable release line. Older release lines should not be assumed to receive backports unless an advisory explicitly says so.
+
+## Reporting a Vulnerability
+
+If you find a security vulnerability, please **do not open a public issue**.
+
+Use GitHub's private vulnerability reporting feature:
+
+- GitHub: https://github.com/Furox-Art/scientific-computing-system/security/advisories/new
+
+You may also contact the maintainer directly. Reports should include the affected version, a minimal reproduction where practical, impact, and any suggested mitigation.
+
+## Threat Model
+
+`scientific-computing-system` is a local-first, pure-Python scientific-computing library distributed through PyPI. The core package has no required runtime dependencies. Optional scientific backends are loaded only when explicitly requested.
+
+### In Scope
+
+| Threat | Mitigation |
+|---|---|
+| **Supply chain: malicious or substituted release artifact** | The release workflow is the sole PyPI publish authority. It builds wheel + sdist on a GitHub-hosted runner, verifies package metadata/version, installs the built wheel, smoke-tests the installed CLI, generates GitHub artifact attestation for those exact runner-local files, and publishes through PyPI Trusted Publishing (OIDC). |
+| **Registry drift** | Public PyPI is treated as the distribution registry. The release integrity check requires exactly one wheel and one sdist on PyPI and requires the matching GitHub Release to contain no wheel/sdist assets. A registry-policy workflow rechecks the public PyPI package and removes accidental distribution assets from GitHub Releases. |
+| **Dependency vulnerabilities** | The core has no required runtime dependencies. Development/test/docs lock files are audited in CI with `pip-audit`; optional backends are isolated behind extras and lazy loading. |
+| **Code execution from package install** | The build backend is `hatchling`; there is no `setup.py` execution and package versioning is static in `pyproject.toml` plus `src/cds/_version.py`. |
+| **Unexpected scientific-tool loading** | Optional tools are selected through an explicit registry/capability layer and are not imported into the zero-dependency core unless requested. |
+| **Untrusted CLI input** | The CLI uses `argparse`-based typed/explicit parsing and does not evaluate arbitrary Python expressions. |
+| **Scientific workflow overclaiming** | The research orchestrator is fail-closed: blocked methods, missing tools, denied approvals, incomplete execution, validation failures, and unresolved method suitability prevent an unqualified final conclusion. |
+
+### Optional Backend Boundary
+
+Optional backends such as SciPy, statsmodels, scikit-learn, SymPy, Z3, h5py, and netCDF4 have their own parser, file-format, numerical, and security behavior. CDS does not make those libraries safe for adversarial input.
+
+In particular, `sympy_verify_identity()` passes caller-provided symbolic strings to SymPy's parser. Do not treat that adapter as a sandbox for hostile expressions. Likewise, HDF5/NetCDF files should be treated according to the security guidance of their respective backend libraries.
+
+### Out of Scope
+
+| Threat | Reasoning |
+|---|---|
+| **Denial of service from intentionally pathological numerical input** | The library is designed for local scientific/research workloads rather than hostile multi-tenant execution. Resource limits should be applied by the host application when processing untrusted inputs. |
+| **Side-channel resistance** | Numerical kernels are not designed or audited as constant-time cryptographic primitives. |
+| **Remote confidentiality guarantees** | The core package does not provide a hosted data service. Applications embedding CDS are responsible for their own storage, access control, and network policy. |
+| **Cryptographic implementation correctness** | CDS is not a cryptographic library and does not provide custom cryptographic primitives. |
+
+## Known Limitations
+
+- **Pure-Python performance:** many core algorithms prioritize transparency and zero required dependencies rather than accelerated throughput. Large numerical workloads should use appropriate optional accelerated backends.
+- **Numerical kernels are not formally verified:** Z3 is available as an optional constraint/formal-verification backend, but that does not imply the numerical library itself has machine-checked proofs.
+- **Optional-backend compatibility is a moving boundary:** backend APIs can change independently of CDS. Pin and test the optional scientific stack used by high-assurance deployments.
+- **Single-maintainer project:** security response and backport capacity are limited compared with a staffed security team.
+
+## Security Best Practices for Users
+
+1. **Pin the package version** in reproducible environments, for example `scientific-computing-system==2.0.0` rather than an unconstrained range.
+2. **Install only the optional extras you need.** Fewer third-party packages reduce supply-chain and compatibility surface.
+3. **Verify provenance for high-assurance use.** Compare the PyPI wheel/sdist SHA-256 digests with the subjects recorded by the GitHub release workflow's artifact attestation.
+4. **Treat optional backend inputs as backend inputs.** Do not pass hostile symbolic expressions or untrusted scientific files without the validation/sandboxing appropriate to SymPy, HDF5, NetCDF, or the relevant backend.
+5. **Keep the environment current.** Review dependency updates and run vulnerability auditing against the exact environment deployed.
+6. **Do not use the library as the sole validation layer for safety-critical conclusions.** Independent domain validation remains necessary.
+
+## Repository Security Controls
+
+CI includes strict type checking, Ruff lint/format checks, full test coverage gates, property-based tests, dependency auditing, CodeQL, and installed-wheel CLI smoke tests across supported operating systems.
+
+These checks are only effective as merge controls when the default branch is protected by a branch rule/ruleset that requires the relevant status checks. Repository administrators should require the aggregate `CI` check, CodeQL, and Installed CLI Smoke before merges and disallow force-push/deletion of `main`.
+
+## Acknowledgments
+
+Responsible disclosures may be credited in the relevant GitHub Security Advisory with the reporter's consent.
+
+## Contact
+
+- Maintainer: Furox-Art (@Furox-Art)
+- Private reporting: https://github.com/Furox-Art/scientific-computing-system/security/advisories/new

scientific_computing_system-2.0.1/benchmarks/robust_runner.py

@@ -0,0 +1,118 @@
+"""Reproducible benchmark runner with robust timing summaries.
+
+This wrapper preserves the benchmark workloads in ``run_benchmarks.py`` while
+replacing its best-of timing helper with warmup + repeated sampling and enriching
+the JSON artifact with enough environment metadata to compare runs responsibly.
+"""
+
+from __future__ import annotations
+
+import math
+import multiprocessing
+import os
+import platform
+import statistics
+import subprocess
+import timeit
+from collections import OrderedDict
+from collections.abc import Callable
+
+import run_benchmarks as legacy
+
+from cds import __version__
+
+_TIMING_SAMPLES: list[dict[str, object]] = []
+_original_build_json = legacy._build_json_record
+
+
+def _percentile(values: list[float], probability: float) -> float:
+    ordered = sorted(values)
+    position = probability * (len(ordered) - 1)
+    low = math.floor(position)
+    high = math.ceil(position)
+    if low == high:
+        return ordered[low]
+    weight = position - low
+    return ordered[low] * (1.0 - weight) + ordered[high] * weight
+
+
+def robust_bench(func: Callable[[], object], number: int, repeat: int = 1) -> float:
+    """Warm up once, collect repeated per-call timings, and return the median."""
+    if number <= 0 or repeat <= 0:
+        raise ValueError("number and repeat must be positive")
+    func()
+    sample_count = max(5, repeat)
+    samples = [timeit.timeit(func, number=number) / number for _ in range(sample_count)]
+    median = statistics.median(samples)
+    mad = statistics.median(abs(value - median) for value in samples)
+    _TIMING_SAMPLES.append(
+        {
+            "index": len(_TIMING_SAMPLES),
+            "number_per_sample": number,
+            "sample_count": sample_count,
+            "median_seconds": median,
+            "mad_seconds": mad,
+            "p95_seconds": _percentile(samples, 0.95),
+            "min_seconds": min(samples),
+            "max_seconds": max(samples),
+            "samples_seconds": samples,
+        }
+    )
+    return median
+
+
+def _full_git_sha() -> str:
+    value = os.environ.get("GITHUB_SHA", "").strip()
+    if value:
+        return value
+    try:
+        result = subprocess.run(
+            ["git", "rev-parse", "HEAD"],
+            capture_output=True,
+            text=True,
+            timeout=5,
+            check=False,
+        )
+    except (OSError, subprocess.SubprocessError):
+        return "unknown"
+    return result.stdout.strip() if result.returncode == 0 and result.stdout.strip() else "unknown"
+
+
+def build_robust_json(
+    results: dict[str, OrderedDict[str, str]],
+) -> dict[str, object]:
+    """Extend legacy benchmark JSON with reproducibility and timing metadata."""
+    record = _original_build_json(results)
+    record["schema_version"] = 2
+    record["package_version"] = __version__
+    record["git_sha_full"] = _full_git_sha()
+    record["environment"] = {
+        "python": platform.python_version(),
+        "implementation": platform.python_implementation(),
+        "platform": platform.platform(),
+        "machine": platform.machine(),
+        "processor": platform.processor() or "unknown",
+        "cpu_count": multiprocessing.cpu_count(),
+    }
+    record["reproducibility"] = {
+        "timing_clock": "timeit.default_timer",
+        "warmup_calls": 1,
+        "minimum_timing_samples": 5,
+        "reported_central_tendency": "median",
+        "dispersion": "median_absolute_deviation",
+        "tail_statistic": "p95",
+        "known_seeds": {"monte_carlo_pi": 42},
+    }
+    record["timing_distributions"] = list(_TIMING_SAMPLES)
+    return record
+
+
+def main() -> None:
+    _TIMING_SAMPLES.clear()
+    legacy._bench = robust_bench
+    legacy._build_json_record = build_robust_json
+    legacy.run_all()
+
+
+if __name__ == "__main__":
+    main()

scientific_computing_system-2.0.1/docs/why-pure-python.md

@@ -0,0 +1,19 @@
+# Why Pure Python?
+
+Fair question. NumPy exists. Why reinvent it?
+
+## 1. Learning
+
+Every algorithm here is readable top to bottom. Want to know how SVD actually works? Open the file. No Fortran, no BLAS calls, no magic.
+
+## 2. Trust
+
+When your simulation gives a weird answer, you can trace every single operation. Try doing that with a compiled LAPACK binding.
+
+## 3. Zero dependencies
+
+pip install and you are done. No MKL vs OpenBLAS drama. No broken wheels on ARM. No version conflicts with your other packages.
+
+## The honest tradeoff
+
+It is slow. For production workloads, use scientific-computing-system-2.0 instead, which wraps NumPy/SciPy with the same philosophy but actual speed.

{scientific_computing_system-2.0.0 → scientific_computing_system-2.0.1}/pyproject.toml

@@ -2,7 +2,7 @@
 # Distribution name. Formerly published as "cognitive-discovery-system";
 # the import name stays `cds`. Keep the old PyPI project alive as an alias.
 name = "scientific-computing-system"
-version = "2.0.0"
+version = "2.0.1"
 description = "A pure-Python computational science platform for numerical methods, modeling, validation, uncertainty, scientific workflows, dimensional analysis, and optional research-data backends. Zero runtime dependencies."
 readme = "README.md"
 license = "MIT"
@@ -11,10 +11,12 @@ requires-python = ">=3.10"
 authors = [
     {name = "Furox-Art", email = "furkanarkn1451@gmail.com"}
 ]
-keywords = ["quantum", "machine-learning", "nlp", "signal-processing", "optimization", "statistics", "probability", "scientific-computing", "numerical-methods", "numerical-integration", "differential-equations", "monte-carlo", "graph-theory", "knowledge-graph", "symbolic-math", "data-analysis", "physics", "linear-algebra", "hypothesis-generation", "pure-python"]
+keywords = ["quantum", "machine-learning", "nlp", "signal-processing", "optimization", "statistics", "probability", "scientific-computing", "numerical-methods", "numerical-integration", "differential-equations", "monte-carlo", "graph-theory", "knowledge-graph", "symbolic-math", "data-analysis", "physics", "linear-algebra", "hypothesis-generation", "pure-python", "reproducibility", "uncertainty-quantification", "sensitivity-analysis", "dimensional-analysis", "scientific-workflows", "ode", "pde"]
 classifiers = [
     "Development Status :: 5 - Production/Stable",
     "Intended Audience :: Science/Research",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
     "Programming Language :: Python :: 3",
     "Programming Language :: Python :: 3.10",
     "Programming Language :: Python :: 3.11",
@@ -23,6 +25,9 @@ classifiers = [
     "Topic :: Scientific/Engineering",
     "Topic :: Scientific/Engineering :: Mathematics",
     "Topic :: Scientific/Engineering :: Physics",
+    "Topic :: Scientific/Engineering :: Artificial Intelligence",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+    "Typing :: Typed",
 ]
 
 dependencies = []

{scientific_computing_system-2.0.0 → scientific_computing_system-2.0.1}/requirements-dev.lock

@@ -4,7 +4,7 @@
 #
 #    pip-compile --extra=dev --extra=docs --extra=test --output-file=requirements-dev.lock pyproject.toml
 #
-anyio==4.14.0
+anyio==4.14.2
     # via
     #   httpx
     #   jupyter-server
@@ -143,7 +143,7 @@ jupyter-events==0.12.1
     # via jupyter-server
 jupyter-lsp==2.3.1
     # via jupyterlab
-jupyter-server==2.20.0
+jupyter-server==2.21.0
     # via
     #   jupyter-lsp
     #   jupyterlab
@@ -364,7 +364,7 @@ six==1.17.0
     # via
     #   python-dateutil
     #   rfc3339-validator
-soupsieve==2.8.4
+soupsieve==2.9.0
     # via beautifulsoup4
 stack-data==0.6.3
     # via ipython

{scientific_computing_system-2.0.0 → scientific_computing_system-2.0.1}/src/cds/_version.py

@@ -1,4 +1,5 @@
 # Static version source. Kept in lockstep with `version` in `pyproject.toml`.
+# Release retry for 2.0.1 after dependency-audit root exclusion.
 # Bump both for a release; merging the version bump to main triggers the
 # verified GitHub + PyPI publish workflow. See `pyproject.toml` for the release
 # checklist. This file is committed (not generated) so mypy has a concrete
@@ -7,5 +8,5 @@ from __future__ import annotations
 
 __all__ = ["__version__", "version", "__version_tuple__", "version_tuple"]
 
-__version__ = version = "2.0.0"
-__version_tuple__ = version_tuple = (2, 0, 0)
+__version__ = version = "2.0.1"
+__version_tuple__ = version_tuple = (2, 0, 1)

{scientific_computing_system-2.0.0 → scientific_computing_system-2.0.1}/src/cds/data_io/__init__.py

@@ -2,6 +2,10 @@
 
 from cds.data_io.streaming import (
     FileProfile,
+    OnlineMoments,
+    StreamingLinearAccumulator,
+    StreamingLinearFit,
+    fit_linear_csv_streaming,
     iter_csv_batches,
     iter_file_blocks,
     open_hdf5,
@@ -11,6 +15,10 @@ from cds.data_io.streaming import (
 
 __all__ = [
     "FileProfile",
+    "OnlineMoments",
+    "StreamingLinearAccumulator",
+    "StreamingLinearFit",
+    "fit_linear_csv_streaming",
     "iter_csv_batches",
     "iter_file_blocks",
     "open_hdf5",