RSeQC
Requirements
- Python 3.9 or later
pip
Check your Python and pip installations:
python3 --version
python3 -m pip --version
Example:
Python 3.11.13
pip 25.3 from /path/to/lib/python3.11/site-packages/pip (python 3.11)
If pip is not installed, follow the official installation instructions:
https://pip.pypa.io/en/stable/installation/
(Optional) Create a Virtual Environment
Using a virtual environment is recommended to keep RSeQC and its dependencies isolated from other Python packages.
Create a new environment:
python3 -m venv rseqc_env
Activate it:
Linux/macOS
source rseqc_env/bin/activate
Windows (PowerShell)
rseqc_env\Scripts\Activate.ps1
Install RSeQC
Install the latest stable release from PyPI
python3 -m pip install rseqc
Install the latest development version from GitHub
python3 -m pip install git+https://github.com/liguowang/RSeQC.git
You can also install a specific branch, tag, or commit.
Install a specific branch:
python3 -m pip install git+https://github.com/liguowang/RSeQC.git@main
Install a specific release tag:
python3 -m pip install git+https://github.com/liguowang/RSeQC.git@v5.0.6
Upgrade RSeQC
Upgrade an existing installation from PyPI:
python3 -m pip install --upgrade rseqc
To upgrade a GitHub installation:
python3 -m pip install --upgrade git+https://github.com/liguowang/RSeQC.git
Uninstall RSeQC
Remove RSeQC:
python3 -m pip uninstall rseqc
Verify the Installation
Check that RSeQC is installed correctly:
bam_stat.py --help
or
python3 -c "from importlib.metadata import version; print('RSeQC', version('RSeQC'))"
License
RSeQC is licensed under the GNU General Public License v3.0 or later (GPL-3.0-or-later).
See the LICENSE file included with this project for the complete license text.
Documentation
Documentation and tutorials are available at:
References
- Wang L, Wang S, Li W. RSeQC: quality control of RNA-seq experiments. Bioinformatics. 2012;28(16):2184-2185. doi:10.1093/bioinformatics/bts356
- Wang L, Nie J, Sicotte H, et al. Measure transcript integrity using RNA-seq data. BMC Bioinformatics. 2016;17:58. doi:10.1186/s12859-016-0922-z
Metadata
Release files for RSeQC 5.0.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 | |
|---|---|---|---|---|
| rseqc-5.0.6.tar.gz | 3.3 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rseqc-5.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.5 MB
Release files / rseqc-5.0.6.tar.gz
| Download URL | rseqc-5.0.6.tar.gz |
|---|---|
| Size | 3.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b361a45ef4a9bb90e926d19abc7801b840897ccad4627f41750972d8cf18cad7
|
|
BLAKE2b-256 checksum How to use checksums |
b35dd2b5a081b28763337630029823c377b94105ea7ff50d39448082d3c253ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.11
|
Release files / rseqc-5.0.6-py3-none-any.whl
| Download URL | rseqc-5.0.6-py3-none-any.whl |
|---|---|
| Size | 210.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b88ff92dece63619a86522710b633fb6f957bf2420d91a7e42b72e7f980ce461
|
|
BLAKE2b-256 checksum How to use checksums |
86d801c8c72d57cf9cd0f6e8a9a1e072aefada49a588088acf3a9b028cb8f03c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.11
|
Security for RSeQC 5.0.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.