# ParseM
## Overview
## Installation
Dependencies:
The BAM parsing is done using c and a few external libraries. At minimum you will need:
gcc libcfu htslib
Notes on installing htslib: For various resons we need to install a statically linked version of htslib. When making use this command instead of just ‘make’:
make CFLAGS=’-g -Wall -O2 -fPIC -static-libgcc -shared’
Then it should be as simple as
pip install ParseM
## Example usage
## Help
If you experience any problems using ParseM, open an [issue](https://github.com/minillinim/ParseM/issues) on GitHub and tell us about it.
## Licence and referencing
Project home page, info on the source tree, documentation, issues and how to contribute, see http://github.com/minillinim/ParseM
This software is currently unpublished
## Copyright
Copyright (c) 2014 Michael Imelfort, Donovan Parks. See LICENSE.txt for further details.
1 maintainer
Metadata
1 maintainer
Release files for ParseM 0.0.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 | Provenance | |
|---|---|---|---|---|
| ParseM-0.0.3.tar.gz | 75.2 kB | Without provenance | Details |
Release files / ParseM-0.0.3.tar.gz
| Download URL | ParseM-0.0.3.tar.gz |
|---|---|
| Size | 75.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a35f0c5eab341e036efdd65d286d3b900dbfd1c9a1bab3a0dd9d863661b34208
|
|
BLAKE2b-256 checksum How to use checksums |
e554d603b8ec5940ab4da0f15908e35f809bb143070bc578db26ec8c451c7dc9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ParseM 0.0.3
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
