Installation
You can install precursor by running:
$ pip install --user precursor
On Linux the executable script can then be found in ~/.local/bin
and on MacOS the script is under /Users/YOURUSERNAME/Library/Python/3.6/bin.
Usage
Typical usage is:
$ precursor.py --autoseeds network targets
For more options you can ask for help as follows:
$ precursor.py --help
usage: precursor.py [-h] [--autoseeds] net inputs
positional arguments:
net metabolic network in SBML format
inputs targets in XML format
optional arguments:
-h, --help show this help message and exit
--autoseeds compute possible seed metabolites
Samples
An archive with sample files is available here.
1 maintainer
Metadata
1 maintainer
Release files for precursor 1.2.4
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 |
|---|---|---|---|---|
| precursor-1.2.4.tar.gz | 6.3 kB | Without provenance | Details for precursor-1.2.4.tar.gz |
Release files / precursor-1.2.4.tar.gz
| Download URL | precursor-1.2.4.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17a6e63fdbf2dc23495aef869d3371024d555907fc8f10a70bc1199c27a93d40
|
|
BLAKE2b-256 checksum How to use checksums |
d8ad025902dc8a21b92ea5d407f344be4a06e33acbbae5b86e658b10bc1c2a4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.8.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.6.6
|
Security for precursor 1.2.4
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.
