cicspi
cicspi is a small SPICE parsing toolbox that reads .subckt definitions into a Python object hierarchy and exposes a simple CLI.
Install
python3 -m pip install cicspi
CLI
Print the node list for a subckt in a SPICE file:
cicspi nodes path/to/netlist.spi my_subckt
Python usage
import cicspi
parser = cicspi.SpiceParser()
parser.parseFile("path/to/netlist.spi")
# SpiceParser is a dict: subckt name → Subckt object
ckt = parser["my_subckt"]
print(ckt.nodes) # list of port node names
print(ckt.instances) # list of SubcktInstance objects
# Collapse bus signals (e.g. A[0], A[1] → A[0:1])
print(ckt.nodesWithBus())
# Iterate instances
for inst in ckt.instances:
print(inst.name, inst.subcktName, inst.nodes)
# Emit SPICE text
print(ckt.tospice())
# JSON round-trip
import json
print(json.dumps(ckt.toJson(), indent=2))
Object model
| Class | Description |
|---|---|
SpiceParser |
dict subclass; maps subckt name → Subckt. Also tracks all instance types in .allinst. |
Subckt |
One .subckt/.ends block. Has .name, .nodes, .instances (list of SubcktInstance), .devices. |
SubcktInstance |
One X-line. Has .name, .subcktName, .nodes, .groupName. |
Device |
Primitive device (future use). |
SpiceObject |
Base class for all objects; provides .properties dict, JSON serialisation, and .nodesWithBus(). |
Release flow
PyPI publishing is handled by GitHub Actions in .github/workflows/release.yml.
Push a tag to trigger a release:
git tag 0.x.y && git push origin 0.x.y
The workflow builds the package, publishes to PyPI via OIDC trusted publishing, and creates a GitHub release with the distribution artifacts attached.
1 maintainer
Metadata
1 maintainer
Release files for cicspi 0.1.6
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 |
|---|---|---|---|---|
| cicspi-0.1.6.tar.gz | 10.4 kB | With provenance | Details for cicspi-0.1.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cicspi-0.1.6-py3-none-any.whl | Python 3 | none | any | Details for cicspi-0.1.6-py3-none-any.whl |
Total release size: 22.0 kB
Release files / cicspi-0.1.6.tar.gz
| Download URL | cicspi-0.1.6.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ac80c99c7d245857734e2b075867200c81a14de91a9e43f9d9ac5fe52fe6082
|
|
BLAKE2b-256 checksum How to use checksums |
73e5f0d3152f291e3a770e245885e2ea9bda5f00bf0496738f02fb3d938392c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 29, 2026.
Transparency logRelease files / cicspi-0.1.6-py3-none-any.whl
| Download URL | cicspi-0.1.6-py3-none-any.whl |
|---|---|
| Size | 11.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b6ffea989d4b24bafffe936c53a9eb5277fe6bc866e9fc01f50f0a8d092fb183
|
|
BLAKE2b-256 checksum How to use checksums |
08116dbaf0f8501625bc5456ccc82bc4e5798a022ff2be6de6be5351ed0ddc9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 29, 2026.
Transparency logSecurity for cicspi 0.1.6
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
Both files in this release have been uploaded with provenance metadata.
Attestation for cicspi-0.1.6.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 Sep 29, 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.
