PiEEG Core
Native accelerator for PiEEG-server. Compiled Rust replacements for hot paths.
⚠️ Early development · experimental · no warranties. This project is in early development — APIs, behavior, and packaging may change without notice. Research/hobbyist software provided as-is, without warranty of any kind, express or implied. Not a medical device. Not intended for clinical, diagnostic, or safety-critical use. Use at your own risk. See LICENSE for full terms.
What it accelerates
| Component | What | Speedup |
|---|---|---|
MultichannelFilter |
Butterworth IIR bandpass (SOS cascade) | ~1057x |
HampelFilter |
Per-channel spike rejection (median + MAD) | ~15x |
decode_channels |
24-bit ADC → µV conversion | ~9x |
When installed, pieeg-server detects it and switches to the compiled implementations automatically. No config needed.
On the Raspberry Pi it additionally provides a native acquisition loop (NativeAcquisition) that owns the SPI/GPIO hardware directly — see Native acquisition.
Benchmark
| Hot path | Python | pieeg-core | Speedup |
|---|---|---|---|
MultichannelFilter (bandpass 1–40 Hz) |
992 samples/s | 1,048,658 samples/s | ~1057× |
HampelFilter (spike removal) |
24,619 samples/s | 358,361 samples/s | ~15× |
decode_channels (24-bit SPI → µV) |
121,352 samples/s | 1,134,301 samples/s | ~9× |
Native acquisition (Raspberry Pi)
Beyond the drop-in DSP accelerators, pieeg-core ships a hard-real-time acquisition loop that reads the ADS1299(s) directly. A dedicated OS thread owns the SPI buses and GPIO lines, polls DRDY, reads both ADC chips, decodes to microvolts and pushes frames into a lock-free single-producer/single-consumer queue — all with the GIL released. Acquisition timing is therefore fully decoupled from CPython's GIL and garbage collector.
This path is compiled only into the Linux/Raspberry Pi wheels (built with the hardware Cargo feature); it depends on spidev and gpio-cdev, so it is absent from the Windows/macOS wheels.
from pieeg_core import NativeAcquisition
acq = NativeAcquisition(
num_channels=16, # 8 (one ADS1299) or 16 (two, PiEEG-16)
sample_rate=250, # 250, 500, 1000, 2000 or 4000 SPS
gpiochip="/dev/gpiochip4",
spi_speed_hz=4_000_000,
cs_pin=19, # chip-select for ADC 2 (16-ch mode)
drdy_pin=26, # DRDY for ADC 1
drdy2_pin=13, # DRDY for ADC 2
queue_capacity=0, # 0 → auto (~4 s of headroom)
)
acq.start() # opens hardware, configures the ADC(s), spawns the read thread
try:
while True:
# Drain up to max_frames buffered samples in FIFO order.
for seq, timestamp, channels in acq.read_batch(max_frames=256):
... # channels is a list of microvolts, len == num_channels
if acq.dropped: # samples lost to consumer back-pressure (ring overflow)
... # counted, never silent
finally:
acq.stop() # signals the read thread and joins it
API
| Member | Description |
|---|---|
start() |
Open the hardware, configure the ADC(s) and spawn the read thread. |
read_batch(max_frames=256) |
Drain up to max_frames buffered samples as a list of (seq, timestamp, [ch1..chN]) tuples in FIFO order. Releases the GIL. |
stop() |
Signal the read thread to stop and join it. Also runs on drop. |
pending |
Frames currently buffered and waiting to be read. |
dropped |
Frames dropped because the consumer fell behind (ring overflow). |
The register-configuration sequence is a faithful port of pieeg_server's PiEEGHardware._configure_adc, with the CONFIG1 data rate parameterised so you can select 250–4000 SPS. Each frame carries a monotonically increasing sequence index internally, so any upstream sample loss is recorded rather than hidden.
The SPI/GPIO paths can only run on a Raspberry Pi with a PiEEG shield. The non-hardware logic (queue, decode, register mapping) is unit-tested off-device.
Install
pip install pieeg-core
Pre-built wheels are published for Linux (x86_64, aarch64, armv7 — including Raspberry Pi), Windows (x86_64) and macOS (arm64) on CPython 3.10–3.13.
Build from source
pip install maturin
cd PiEEG-core
maturin develop --release
To include the native acquisition loop (Raspberry Pi only), enable the hardware feature:
maturin develop --release --features hardware
Build inside the same Python environment where pieeg-server is installed.
1 maintainer
Metadata
1 maintainer
Release files for pieeg-core 0.3.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 | |
|---|---|---|---|---|
| pieeg_core-0.3.0.tar.gz | 231.1 kB | With provenance | Details |
Built distributions (wheels)
Total release size: 4.5 MB
Release files / pieeg_core-0.3.0.tar.gz
| Download URL | pieeg_core-0.3.0.tar.gz |
|---|---|
| Size | 231.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04c9757f0db317936ff7ddc73c14c96252aab32e8e87366d76e502c01119c484
|
|
BLAKE2b-256 checksum How to use checksums |
3830a05258ad070c6ba0d0ec715825070ea7342175ceb6ac89c4d0b085f2352c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp313-cp313-win_amd64.whl
| Download URL | pieeg_core-0.3.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 148.7 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
5e9bbadc03a91ef4c2203c364f209cf0476bdf9db5fd2de39a479e7f1ec03551
|
|
BLAKE2b-256 checksum How to use checksums |
0b60f9aecc4569130e009eea44e0d23d9ebeb2230bb59c8a6875aef4f7cd1cee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pieeg_core-0.3.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 236.9 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
a44a4a0f0efda3630139730b86bd9aeae1dd68268905915b8dc1cfa4251e7d32
|
|
BLAKE2b-256 checksum How to use checksums |
5edef081e7cfa8856284b12085f2a4d5263e044995c4403476755c47a53295a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp313-cp313-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
| Download URL | pieeg_core-0.3.0-cp313-cp313-manylinux_2_17_armv7l.manylinux2014_armv7l.whl |
|---|---|
| Size | 237.9 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARMv7l |
|
SHA-256 checksum How to use checksums |
d78cf4908a4b9ee9e6ee6aabd45883f8a7b7aa640f8bf3f8fc45b5feb5b70833
|
|
BLAKE2b-256 checksum How to use checksums |
1ad5b7e02bd7fda58ed6958a0ec74b5b466edea73a341b9759075588025f0ff2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pieeg_core-0.3.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 229.1 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
5d84852b35a8c3bb550465476046e25772a91ff9e628abcc5fbe4e7db6c44808
|
|
BLAKE2b-256 checksum How to use checksums |
94157fc8fc8f0e66b280534d9342e484ab546f9786528263077627a25007ba1f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | pieeg_core-0.3.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 216.5 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
2c0282e4c0354ccc22ddf48af1a68f162273f59d811101f2b07e795c3a4369bf
|
|
BLAKE2b-256 checksum How to use checksums |
e011952089039463540febc1d0d2516031e53e9d9ab1d1d998af9d823274dbed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp312-cp312-win_amd64.whl
| Download URL | pieeg_core-0.3.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 149.1 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
3537cb44ada19344cdbe4982def5777523e5d7eddae8dcdcf8be5e760023c801
|
|
BLAKE2b-256 checksum How to use checksums |
d5905ec328581fca71881e112bf3050f029ebf5a42496d2cc9d34347d3690b7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pieeg_core-0.3.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 237.3 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
5f0bc21fd4c8a8595e52c31870f454533cf21879461857b9e8174fb471454c99
|
|
BLAKE2b-256 checksum How to use checksums |
245833111d9f1ddde1e55a2b99c03355db7ce65bd480235dd92585e8f51918ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp312-cp312-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
| Download URL | pieeg_core-0.3.0-cp312-cp312-manylinux_2_17_armv7l.manylinux2014_armv7l.whl |
|---|---|
| Size | 238.2 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARMv7l |
|
SHA-256 checksum How to use checksums |
deaaa2d22b21080f11bb23518badcaf332e443576b55035d6d261a6262b63f77
|
|
BLAKE2b-256 checksum How to use checksums |
23af43f67501bd95aa3e198def8630402ce85235aec77c85269a21a09de1a59c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pieeg_core-0.3.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 229.6 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
c74c4dea0601173432aa4684f513806e155282cc670f2ac263f477c7aaa0ad41
|
|
BLAKE2b-256 checksum How to use checksums |
e52f77a91d79127e1ee8757d2fb786e5dbf9d5a25fab6063c0270f4c996b8682
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | pieeg_core-0.3.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 217.0 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
733863b358aebf7ad700b3428e852d466d35ddcfa6a48a8d7497bdf74618c15f
|
|
BLAKE2b-256 checksum How to use checksums |
a5185168ba816f6aa3a2b01968f3d839bbc9808d1214edab744787d44256ea3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp311-cp311-win_amd64.whl
| Download URL | pieeg_core-0.3.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 148.2 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8262179ab26f37809b804655395273c5d2d85ab2081b13aba119f4fff39490b0
|
|
BLAKE2b-256 checksum How to use checksums |
a44fc39c0f1f8d1757ef6b25f37d0b8df8d68ec691ffd8ca5b276f24ee942196
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pieeg_core-0.3.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 237.0 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
36686dd1a9bb3788ee83fc67a166fba855bb8fe30fd4f3a12313a146b0877c43
|
|
BLAKE2b-256 checksum How to use checksums |
abe0b73bff2bdca729ea59f010d64e813e55559bcd6ddb05af254524cb17bf64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp311-cp311-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
| Download URL | pieeg_core-0.3.0-cp311-cp311-manylinux_2_17_armv7l.manylinux2014_armv7l.whl |
|---|---|
| Size | 238.1 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARMv7l |
|
SHA-256 checksum How to use checksums |
542a6e89fa3ce6741118c5e5f32ce777b47d3a526140d15d04ba1088fdb4ccdc
|
|
BLAKE2b-256 checksum How to use checksums |
93e762ab8b19044dc03f008a8856dc8cfc52d8bfec42179c3fa86772acd1887f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pieeg_core-0.3.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 229.7 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
28bb8016ac7ed1777e29c24bbace2f522c923abeecc15d35c2662740a73a24a2
|
|
BLAKE2b-256 checksum How to use checksums |
73cd0d4d6aece0cf708c70cc628837aab6975cafc2d4d8f5384c496d9f6a8658
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | pieeg_core-0.3.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 217.0 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0fffa2fb1c0d23ee77d4a21574c36ed79a0b2bc6c3ec17c645ed7376facfd0b5
|
|
BLAKE2b-256 checksum How to use checksums |
f31229af1ece63ce1e009f5147ff3f8c02e18ac5e1769b08099057701e899e36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp310-cp310-win_amd64.whl
| Download URL | pieeg_core-0.3.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 148.2 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7e2689dbc223fc23b27206deb7d9597ba6af2386f6658c6cdd96a3b56c45792a
|
|
BLAKE2b-256 checksum How to use checksums |
bd82905053887d379afa2a1418498a6da1e1360a13b694d962d19673e2585ded
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pieeg_core-0.3.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 237.2 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
4e7d167b1950c7dc9e0d3b0653f5bb18cf19cf057eef203b3b483087aab7456e
|
|
BLAKE2b-256 checksum How to use checksums |
a538dc1c0925f3d70cbfa4dfde3a54f3ceab897702fb491d32c59f54fa9ae8e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp310-cp310-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
| Download URL | pieeg_core-0.3.0-cp310-cp310-manylinux_2_17_armv7l.manylinux2014_armv7l.whl |
|---|---|
| Size | 238.2 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARMv7l |
|
SHA-256 checksum How to use checksums |
375502ebcc0da98ce7ea59c43bb031fad96934c9fb3724f2b17a486cb2574bd7
|
|
BLAKE2b-256 checksum How to use checksums |
287dc85c60e554385ccf02e75b834a0d187901f7ccfc0ad1c578e0e706d09185
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pieeg_core-0.3.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 229.9 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
cd9ef9db1a5ec49199b6b99c9d8b2be09e8faa7844677ac185f9fef16b72c081
|
|
BLAKE2b-256 checksum How to use checksums |
082119676d5e24917c0a33e931fd61be975fb47944d673c00ba998248bc4b72c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / pieeg_core-0.3.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | pieeg_core-0.3.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 217.1 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
92fa559caba46e4183e418922821c8367d7cb9b504797ac842d061774d4248e5
|
|
BLAKE2b-256 checksum How to use checksums |
f9825890e0d1ef688eb3f85d1b808ab393d6b2e9e2dfca509b808d8ee35be705
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logSecurity for pieeg-core 0.3.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 21 files in this release have been uploaded with provenance metadata.
Attestation for pieeg_core-0.3.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 Jul 13, 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.
