pypulseqpp-seqeyes
SeqEyes, the Pulseq sequence viewer,
built for pypulseqpp's Sequence.plot. It is installed with
pip install 'pypulseqpp[plot]' and is not needed for anything else.
The wheel carries the SeqEyes program and no Qt: it runs on the Qt that
PySide6-Essentials installs. pypulseqpp-seqeyes file.seq opens a file
from the command line, with SeqEyes' own options.
Linux
PySide6's Qt draws with the system's display libraries. A desktop has them; a bare server or container needs, on Debian or Ubuntu,
# For offscreen rendering with QT_QPA_PLATFORM=offscreen
sudo apt install libegl1 libgl1 libx11-6 libdbus-1-3 libfontconfig1 \
libfreetype6 libglib2.0-0 libxkbcommon0
# And to open a window under X11 (Wayland needs none of these)
sudo apt install libx11-xcb1 libxkbcommon-x11-0 libxcb1 libxcb-cursor0 \
libxcb-icccm4 libxcb-image0 libxcb-keysyms1 libxcb-randr0 \
libxcb-render-util0 libxcb-render0 libxcb-shape0 libxcb-shm0 \
libxcb-sync1 libxcb-util1 libxcb-xfixes0 libxcb-xkb1
libxcb-cursor0 is the one an Ubuntu desktop may lack: Qt needs it to open an
X11 window, and says so if it is missing.
Licence
GPL-3.0-or-later. SeqEyes is BSD-3-Clause (seqeyes/LICENSE, and
seqeyes/licenses/license_safe_pns for its PNS model); QCustomPlot, the
plotting widget compiled into it, is GPL-3.0-or-later, so the program they
make is too. pypulseqpp itself is MIT and does not depend on this package.
Building
SeqEyes is the submodule in seqeyes/, pinned to a release and built as it
stands. A build needs Qt 6.8 or later, found through CMAKE_PREFIX_PATH:
git submodule update --init --recursive
CMAKE_PREFIX_PATH=/path/to/Qt/6.8.3/gcc_64 pip install ./viewer
The release wheels are built by cibuildwheel, configured in pyproject.toml.
Release files for pypulseqpp-seqeyes 0.3.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pypulseqpp_seqeyes-0.3.3.tar.gz | 3.7 MB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pypulseqpp_seqeyes-0.3.3-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| pypulseqpp_seqeyes-0.3.3-py3-none-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl | Python 3 | none | Linux glibc 2.28+ x86-64, Linux glibc 2.24+ x86-64 | Details |
| pypulseqpp_seqeyes-0.3.3-py3-none-macosx_10_9_universal2.whl | Python 3 | none | macOS 10.9+ universal2 (ARM64, x86-64) | Details |
Total release size: 9.3 MB
Release files / pypulseqpp_seqeyes-0.3.3.tar.gz
| Download URL | pypulseqpp_seqeyes-0.3.3.tar.gz |
|---|---|
| Size | 3.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de3df005fe5f245c080df693d34e6c05d44ce0367df09abc1d8c81aa2e163e55
|
|
BLAKE2b-256 checksum How to use checksums |
70cceca4faeeeebaab8e513f5b1196552fd480dbbc4eb83f9c6efa9770c02ea4
|
| 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 14, 2026.
Transparency logRelease files / pypulseqpp_seqeyes-0.3.3-py3-none-win_amd64.whl
| Download URL | pypulseqpp_seqeyes-0.3.3-py3-none-win_amd64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
dffb7e25a07852c17e42390e9abbb38725afb6af2d965c3efd5282a249e4e826
|
|
BLAKE2b-256 checksum How to use checksums |
e7d54b6c9f1d57b00a552ca20b2aec7eff420d5772dfbe1181c184ee9e728b68
|
| 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 14, 2026.
Transparency logRelease files / pypulseqpp_seqeyes-0.3.3-py3-none-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pypulseqpp_seqeyes-0.3.3-py3-none-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | Linux glibc 2.24+ x86-64 Linux glibc 2.28+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
c298e44d8fe74bc55d113e00e9bec4e15b38c59cc3df7c9812991482873b8ae2
|
|
BLAKE2b-256 checksum How to use checksums |
9d55c27f9ccbd8099ad2a17cbf7d432ab61801371f3bb364a43b33fb110606a7
|
| 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 14, 2026.
Transparency logRelease files / pypulseqpp_seqeyes-0.3.3-py3-none-macosx_10_9_universal2.whl
| Download URL | pypulseqpp_seqeyes-0.3.3-py3-none-macosx_10_9_universal2.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Python 3 macOS 10.9+ universal2 (ARM64, x86-64) |
|
SHA-256 checksum How to use checksums |
a227b07170032d66b95dd640c5810173a93a742e0826f0fd1bec46b719c0c138
|
|
BLAKE2b-256 checksum How to use checksums |
fcac59b23905d1cbada055ae53bbad1af6dd4e9d829f2f26056b7495c7d7bf7b
|
| 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 14, 2026.
Transparency log