spice3
pip install spice3 → import spice.
Circuit simulation for Python, powered by Dune — a Rust engine derived from Berkeley SPICE3f5 and validated circuit-by-circuit against ngspice as numerical oracle.
Status: pre-alpha. This release reserves the package name while the engine's first public version is being finished. The API below works today but may still change.
from pathlib import Path
import spice
result = spice.simulate(Path("rc.cir"))
plot = result.plot("Transient Analysis")
df = plot.df() # polars DataFrame, scale column first
v2 = plot.column("v(2)") # zero-copy, read-only numpy array
- Every SPICE3f5 analysis:
.op,.dc,.tran,.ac,.pz,.noise,.disto,.tf,.sens— plus the periodic steady state of driven circuits (.pss, shooting–Newton;spice.pss()). - All SPICE3f5 devices, including BJT (Gummel–Poon), MOS levels 1/2/3/6, BSIM1/BSIM2, JFET, MESFET, switches and both transmission lines.
- Results as polars DataFrames (pandas optional)
and zero-copy NumPy arrays; complete type annotations (
py.typed). - Schematics as decks:
spice.pic.extract()reads the netlist of an rpic figure drawn with the dune prelude,spice.simulate()runs it andspice.pic.render()draws it as SVG (with typeset$...$labels). - Faithful netlist semantics: decks that run under
spice3 -borngspice -brun here, with structured, span-carrying errors.
The engine, corpus and oracle harness live in the Dune repository. BSD-3-Clause, © André Leite and The Regents of the University of California.
1 maintainer
Metadata
1 maintainer
Release files for spice3 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| spice3-0.1.0.tar.gz | 737.8 kB | With provenance | Details for spice3-0.1.0.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| spice3-0.1.0-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details for spice3-0.1.0-cp310-abi3-win_amd64.whl |
| spice3-0.1.0-cp310-abi3-manylinux_2_39_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.39+ x86-64 | Details for spice3-0.1.0-cp310-abi3-manylinux_2_39_x86_64.whl |
| spice3-0.1.0-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details for spice3-0.1.0-cp310-abi3-macosx_11_0_arm64.whl |
| spice3-0.1.0-cp310-abi3-macosx_10_12_x86_64.whl | CPython 3.10 | abi3 | macOS 10.12+ x86-64 | Details for spice3-0.1.0-cp310-abi3-macosx_10_12_x86_64.whl |
Total release size: 15.8 MB
Release files / spice3-0.1.0.tar.gz
| Download URL | spice3-0.1.0.tar.gz |
|---|---|
| Size | 737.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b81ac843693270faa913c792c9a2de2b1e6a68ad9c6f15c428c5e1e1c72bf16
|
|
BLAKE2b-256 checksum How to use checksums |
6885846ee8e57363ebad78f614f48de775d8c5a86e8b3f43158e727ea85816dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / spice3-0.1.0-cp310-abi3-win_amd64.whl
| Download URL | spice3-0.1.0-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 4.0 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
6429c11755c78ac7317d25fb25f106750c530fd69494c545b84c0a61c6836fff
|
|
BLAKE2b-256 checksum How to use checksums |
2ecd9caf96a69c379741124b819f37e77d4fb4b1f8960ade9408efb1accc85cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / spice3-0.1.0-cp310-abi3-manylinux_2_39_x86_64.whl
| Download URL | spice3-0.1.0-cp310-abi3-manylinux_2_39_x86_64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | CPython 3.10 Linux glibc 2.39+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
6faad8ab5e60deb5e4004fcf30e96f04f4b22c1f5c1ff631c82697bcc6f70e59
|
|
BLAKE2b-256 checksum How to use checksums |
bc56f14cbcd87ed5323d27f3423d0e272a5a26083e0c0072cfca66504eacaa7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / spice3-0.1.0-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | spice3-0.1.0-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.3 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
70fc420a7f1a043325baf0e14fc8d374bb557517e35b564ae75a90c58fff3db6
|
|
BLAKE2b-256 checksum How to use checksums |
7ba314e147cf229eb26a8ec398c28b889bc726ae3caa3c308b65c2ac95b9de11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / spice3-0.1.0-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | spice3-0.1.0-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 3.7 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
e06f11aa260241faf457f01627789612c48ed24dc61031c499a0f8837bd78d18
|
|
BLAKE2b-256 checksum How to use checksums |
ae07c22afd0cc21dc0eb905bec70203e97b6515ecda2d6e63eabeed989a4355d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logSecurity for spice3 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 5 files in this release have been uploaded with provenance metadata.
Attestation for spice3-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
