pypulseqpp is a fast drop-in replacement for PyPulseq, written in Python with a C++ backend. You write MR pulse sequences exactly as you write them in PyPulseq, and get back a sequence that is fast to build, check and write, however long it is. Change one line of your script,
import pypulseqpp as pp # in place of: import pypulseq as pp
and it runs: the event factories, Opts and the Sequence methods keep
PyPulseq's names, arguments and units. Underneath, the sequence is stored by a
C++ core, so a scan of a million blocks is built, deduplicated and written in
seconds.
You write the sequence; pypulseqpp does the rest. It stores and deduplicates your events, writes Pulseq text and binary files that any Pulseq interpreter plays, and checks the result against your scanner: timing, gradient amplitude and slew rate, peripheral nerve stimulation, mechanical resonances, acoustic noise and SAR.
How it works
A Pulseq sequence is a list of blocks played back to back, and each block holds at most one event per channel: an RF pulse, a gradient on each axis, an ADC window, a delay. You build it in five steps:
- Describe your scanner: field strength, gradient amplitude and slew-rate
limits, raster times and dead times. This is the
systemobject, app.Opts. - Design the events with the factories (
pp.make_sinc_pulse,pp.make_trapezoid,pp.make_adc...). Each one is solved againstsystem, so a gradient you ask for by its area comes back as the shortest trapezoid your hardware plays. - Add the events to the sequence block by block, in a loop over the lines of k-space.
- Check it.
seq.check_timing()checks every block against the rasters and dead times; the gradient, PNS, mechanical-resonance and SAR checks look at the whole scan. - Write the
.seqfile, and play it on the scanner through your vendor's Pulseq interpreter.
Here is a 2D gradient echo, written the PyPulseq way:
import numpy as np
import pypulseqpp as pp
system = pp.Opts(max_grad=32, grad_unit="mT/m", max_slew=130, slew_unit="T/m/s")
fov, n = 256e-3, 64
rf, gz, gz_reph = pp.make_sinc_pulse(
flip_angle=np.deg2rad(15),
duration=2e-3,
slice_thickness=5e-3,
time_bw_product=4,
system=system,
return_gz=True,
)
gx = pp.make_trapezoid("x", flat_area=n / fov, flat_time=3.2e-3, system=system)
adc = pp.make_adc(n, duration=gx.flat_time, delay=gx.rise_time, system=system)
gx_pre = pp.make_trapezoid("x", area=-gx.area / 2, duration=1e-3, system=system)
seq = pp.Sequence(system)
for line in range(n):
gy_pre = pp.make_trapezoid(
"y", area=(line - n / 2) / fov, duration=1e-3, system=system
)
seq.add_block(rf, gz)
seq.add_block(gx_pre, gy_pre, gz_reph)
seq.add_block(gx, adc)
seq.add_block(pp.make_delay(10e-3))
ok, errors = seq.check_timing()
seq.write("gre.seq")
Sequences as functions
A script designs one protocol. Put the same code in a function of system
and keyword arguments, and it designs any protocol you ask for:
def gre(system, *, fov=256e-3, n=64, flip_angle_deg=15.0) -> pp.Sequence:
...
return seq
- The keyword arguments are your protocol. Document each in a NumPy-style
Parameterssection, with its unit, andpp.cli.run(gre)turns them into a command line. - Return the sequence, or a list of sequences when the scan has prescans; the main sequence goes last.
- This is the shape pulserver expects, so the same function becomes a sequence the operator edits in the scanner UI.
pypulseqpp ships 28 sequences written this way (gradient echo, spin echo, FSE, MPRAGE, bSSFP, EPI, ZTE, with Cartesian, radial, spiral and PROPELLER readouts), each one a module you can call or run from the command line:
from pypulseqpp import sequences
seq = sequences.gre2D_sequence(n_x=64, n_y=64)
python -m pypulseqpp.sequences.sequence.gre2D_sequence --help
They are built from sequence modules, ready-made excitations, preparations and readouts that you can reuse in your own functions.
The checks compute estimates. Passing them does not establish scanner or patient safety.
Installation
pip install pypulseqpp
Wheels are published for Linux x86-64, macOS (Apple silicon and x86-64) and Windows AMD64, Python 3.10 to 3.14.
Learn more
- Course: ten lessons from a pulse-acquire experiment to your own sequence module.
- Sequence catalogue: every shipped sequence, with its protocol and diagram.
- From a PyPulseq script: your script, and the same script as a sequence function.
- Documentation, for every option and API detail.
How to cite
pypulseqpp has no publication of its own. If you use it, please cite Pulseq and PyPulseq:
@article{layton2017pulseq,
title = {Pulseq: a rapid and hardware-independent pulse sequence prototyping framework},
author = {Layton, Kelvin J and Kroboth, Stefan and Jia, Feng and Littin, Sebastian
and Yu, Huijun and Leupold, Jochen and Nielsen, Jon-Fredrik
and St{\"o}cker, Tony and Zaitsev, Maxim},
journal = {Magnetic Resonance in Medicine},
volume = {77},
number = {4},
pages = {1544--1552},
year = {2017},
doi = {10.1002/mrm.26235}
}
@article{ravi2019pypulseq,
title = {PyPulseq: A Python Package for MRI Pulse Sequence Design},
author = {Ravi, Keerthi Sravan and Geethanath, Sairam and Vaughan, John Thomas},
journal = {Journal of Open Source Software},
volume = {4},
number = {42},
pages = {1725},
year = {2019},
doi = {10.21105/joss.01725}
}
License
MIT, except bundled or vendored third-party components, which keep their own licences. See License and third-party notices.
1 maintainer
Metadata
1 maintainer
Release files for pypulseqpp 0.0.48
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 |
|---|---|---|---|---|
| pypulseqpp-0.0.48.tar.gz | 1.7 MB | With provenance | Details for pypulseqpp-0.0.48.tar.gz |
Built distributions (wheels)
Total release size: 27.9 MB
Release files / pypulseqpp-0.0.48.tar.gz
| Download URL | pypulseqpp-0.0.48.tar.gz |
|---|---|
| Size | 1.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
efe07ffab2a338b364eae462bdd87f7094d6a325d337749b72e91f33cbf91fda
|
|
BLAKE2b-256 checksum How to use checksums |
16e66184a93eed07eb80e64c4d8db5c8dc8f0d09e1c8aeb2b34a1b7d67b784d0
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp314-cp314-win_amd64.whl
| Download URL | pypulseqpp-0.0.48-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
ec343633e8ec2e509f8e3e76b45118f0a636b7c5e42d202b1258920968887dcd
|
|
BLAKE2b-256 checksum How to use checksums |
0d70f28e1fa4b32c24a352fe2089afecc8c13ac2832f364a587f4e4f1b1cb83a
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pypulseqpp-0.0.48-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
f9d6b38d2bb6f40ae2b5725e028ea815c2b76ff28c577067707ada81acbd8ce4
|
|
BLAKE2b-256 checksum How to use checksums |
bcd534df2c8161b811f84d40ded965d67677732d75f6fc006670a3ac4c5ca242
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | pypulseqpp-0.0.48-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3f9df5133f18da46c48690c58fb937a46c0a6acae8de17d2f7bfd3ffcf720b82
|
|
BLAKE2b-256 checksum How to use checksums |
cdebb359c8ec3865110ba3f0f323e74b6075e34e0a8cc00a9dc863b0a6a98db7
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp314-cp314-macosx_10_15_x86_64.whl
| Download URL | pypulseqpp-0.0.48-cp314-cp314-macosx_10_15_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.14 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
9f141efbc00f07085734c057919997b658314c35301c9234c72fcc0ae826aac1
|
|
BLAKE2b-256 checksum How to use checksums |
163fce8be6d38cb56e29d07246b02df343f4eea24a5edeb205404bf119f4820d
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp313-cp313-win_amd64.whl
| Download URL | pypulseqpp-0.0.48-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
ef25d08db789f02134bc80dbd70c7204d16d124d6008c10cf9552a31f17d0761
|
|
BLAKE2b-256 checksum How to use checksums |
1fd1b3bb00969cbc97e7389ca51e1a349bd3a4d075a50c11934cbfb94604e8f7
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pypulseqpp-0.0.48-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
1a364a18626ec63b38affdae619b28bf1365c634c30eaf4fee500cf547cb61e3
|
|
BLAKE2b-256 checksum How to use checksums |
0cf6da2ee31bdbfe70b4421cccf0800ea7949208f4f93f5366e2edd9f62cd2e5
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | pypulseqpp-0.0.48-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6564908f769e88c330f50d2551071954a834ee7e3107c700dd6f949ea374e756
|
|
BLAKE2b-256 checksum How to use checksums |
b783ace953e341c24aecacc48592d8daf0d96369f6ae43e950a4502a73135e83
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp313-cp313-macosx_10_13_x86_64.whl
| Download URL | pypulseqpp-0.0.48-cp313-cp313-macosx_10_13_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.13 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
1c1536dcba4caaf73f39e1cffff4f51af7f27cd4bf219e98954977d65b3bac0b
|
|
BLAKE2b-256 checksum How to use checksums |
662a214127a6222bcaa183f8540067d4ca4f3de95b44a4e968aab361fd94ac21
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp312-cp312-win_amd64.whl
| Download URL | pypulseqpp-0.0.48-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
eb978936f10ece9ce062425f762699049896e781b4a7bd8bc8493557024fa682
|
|
BLAKE2b-256 checksum How to use checksums |
166e33fbff3ed3511430d1f5f83e37c4b837088f653b73e3ce86ff183fd4ad92
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pypulseqpp-0.0.48-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
9073c4211e7cdb1d190b6616d7a5de0970ba80971cae80148eeeaaeeb028f8a4
|
|
BLAKE2b-256 checksum How to use checksums |
9b6ce06aea82394d04aea8111352b68c87834e3e7be537d6a5482f6114699b48
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | pypulseqpp-0.0.48-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
81e27b1c69859f1ab1544772d2a658a635f11c79bb700ace54ba9a14c9a93d38
|
|
BLAKE2b-256 checksum How to use checksums |
74dc4bf5901105dd83d71df3b96680c4c6baa847b40c16376140f21b910226f4
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | pypulseqpp-0.0.48-cp312-cp312-macosx_10_13_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.12 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
74fc9f355bad72b63396f2e706ef7fa44212f5a86d6347cd954efedfc6d955ae
|
|
BLAKE2b-256 checksum How to use checksums |
c6b425c13b7c3e9bc7a1e276e8b07aea88956c69753664bfd4a880b87e1da5a6
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp311-cp311-win_amd64.whl
| Download URL | pypulseqpp-0.0.48-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
fe449d00fb74f7b4f30bd6f7f06b908a10300c654b564ece570b5f7f68e5398e
|
|
BLAKE2b-256 checksum How to use checksums |
13b44d3900155194109e878e7dae2a40a0eb4461c08a79389b017be8d824c629
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pypulseqpp-0.0.48-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
c4fd44369b0ffe63948812d8f942ee2d90253cea7e4dc962e52b5191528a6f88
|
|
BLAKE2b-256 checksum How to use checksums |
6cea9fa160750f62af2a1f74b758bebfdf0a1710d51d5e281c897b5cd94b787d
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | pypulseqpp-0.0.48-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
7d6736aff8521928bf51423d8a412e8b2846bf8159357d200ac5d6af9fdd9a77
|
|
BLAKE2b-256 checksum How to use checksums |
2c41aa375be200821c21bfd089dc23d6bc3f24365271f47091368787f3ac98ad
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp311-cp311-macosx_10_9_x86_64.whl
| Download URL | pypulseqpp-0.0.48-cp311-cp311-macosx_10_9_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.11 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
e1c27d1675c1353a820526888ca482cb02e0673ef94fa53a139b44aaa62f5f35
|
|
BLAKE2b-256 checksum How to use checksums |
10a19abbb04a34cb4c351b12f4b3dbbf88e5224fc31a573630106011eaa2ef55
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp310-cp310-win_amd64.whl
| Download URL | pypulseqpp-0.0.48-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
21201670e928f4b985b4c71239ddd1aefb055c6ed039dfc18284c3a11bf5080d
|
|
BLAKE2b-256 checksum How to use checksums |
84c58bd99979a8257a7010298429e1e556fea7fa6adc6cca47e668f5d5e30f4f
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pypulseqpp-0.0.48-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
5981352155befb868a69b57c7d340aad59c5c438565d61d5bafe70cd8a7fe294
|
|
BLAKE2b-256 checksum How to use checksums |
31bab9edbd796e0442e5924b579ff16c15de54cf13444278302b839e2c0357a7
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | pypulseqpp-0.0.48-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
f6078d49bd5030ee8e344d2a89eeb2d9ce82318afe9be1d757ca33026551453c
|
|
BLAKE2b-256 checksum How to use checksums |
a7018dccafef7fc31ae78851d28783a0c8f4b6eda23e996256bbc992cc076296
|
| 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 Oct 22, 2026.
Transparency logRelease files / pypulseqpp-0.0.48-cp310-cp310-macosx_10_9_x86_64.whl
| Download URL | pypulseqpp-0.0.48-cp310-cp310-macosx_10_9_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.10 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
b86f4d8ca284b0badea8256e0e9203b94fe1e41928722bf69978b2ababf2cec4
|
|
BLAKE2b-256 checksum How to use checksums |
dbd6c8fb6a93befdbc93e74bc2ae9baff9deb489ac2b2481dd12e215ce4cdaa0
|
| 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 Oct 22, 2026.
Transparency logSecurity for pypulseqpp 0.0.48
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 pypulseqpp-0.0.48.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 Oct 22, 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.
