itpseq: A Python module and command-line tool for the analysis of iTP-Seq data.
The latest documentation is available at itpseq.readthedocs.io.
Dependencies
itpseq runs on Python 3.9+ on Linux, MacOS, and Windows.
Installation requires regex, numpy, pandas, matplotlib, seaborn, pydeseq2, logomaker, Jinja2, weasyprint, ipython, click, and ipywidgets. The dependencies are installed automatically when installing from pip.
Installation
The latest stable release (and required dependencies) can be installed from PyPI:
pip install itpseq
To update the package to the latest version, run:
pip install -U itpseq
After installation, if Python and pip are configured correctly, the "itpseq" command should be available in the terminal. If not, one should ensure the location of the executable is in the PATH.
Citing
Known issues
On MacOS and Windows, the "weasyprint" library that is used to produce the PDF version of the report seems to have an issue and exporting a PDF report is currently not possible. It is nevertheless possible to produce an HTML report by running:
itpseq report -o report.html data_directory
in place of:
itpseq report data_directory
Metadata
Release files for itpseq 1.0.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 | |
|---|---|---|---|---|
| itpseq-1.0.0.tar.gz | 3.1 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| itpseq-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.3 MB
Release files / itpseq-1.0.0.tar.gz
| Download URL | itpseq-1.0.0.tar.gz |
|---|---|
| Size | 3.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc46707f149249835b0ec81540c5acf64039e38b6b4041b41965d55936cbfc1e
|
|
BLAKE2b-256 checksum How to use checksums |
8790299707d7bcf8733b2f2b01bbc418cd3443e559cdee72cc26b2c27ca77dac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 19, 2025.
Transparency logRelease files / itpseq-1.0.0-py3-none-any.whl
| Download URL | itpseq-1.0.0-py3-none-any.whl |
|---|---|
| Size | 3.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8394095fa1b2b2e2d2dc70c8d9e98076d054265ef6fbf105805e3a6e2135096
|
|
BLAKE2b-256 checksum How to use checksums |
7c0580b2a78e2ab7794c8fbd38efdc24ca4b3fd414517f7c5f7cccc1cf2c83ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 19, 2025.
Transparency logSecurity for itpseq 1.0.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 2 files in this release have been uploaded with provenance metadata.
Attestation for itpseq-1.0.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 Sep 19, 2025.
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.