Bio2BEL KEGG 
This package allows the enrichment of BEL networks with KEGG information by wrapping its RESTful API. Furthermore, it is integrated in the ComPath environment for pathway database comparison.
If you find this package useful, please consider citing [domingofernandez2018]:
Domingo-Fernandez, D., et al (2018). ComPath: an ecosystem for exploring, analyzing, and curating mappings across pathway databases. Npj Systems Biology and Applications, __5__(1), 3.
Warning This package creates partOf relationships in BEL, but does not convert KEGG mechanistic relationships to BEL. That functionality is implemented in the PathMe project.
Installation 
bio2bel_kegg can be installed easily from PyPI with the following code in your favorite terminal:
$ pip install bio2bel_keggor from the latest code on GitHub in development mode with:
$ git clone https://github.com/bio2bel/kegg.git
$ cd kegg
$ pip install -e .Setup
KEGG can be downloaded and populated from either the Python REPL or the automatically installed command line utility.
Python REPL
>>> import bio2bel_kegg
>>> kegg_manager = bio2bel_kegg.Manager()
>>> kegg_manager.populate()Command Line Utility
bio2bel_kegg populateOther Command Line Utilities
Run an admin site for simple querying and exploration
python3 -m bio2bel_kegg web(http://localhost:5000/admin/)Export gene sets for programmatic use
python3 -m bio2bel_kegg export
Citation
Kanehisa, Furumichi, M., Tanabe, M., Sato, Y., and Morishima, K.; KEGG: new perspectives on genomes, pathways, diseases and drugs. Nucleic Acids Res. 45, D353-D361 (2017).
Kanehisa, M., Sato, Y., Kawashima, M., Furumichi, M., and Tanabe, M.; KEGG as a reference resource for gene and protein annotation. Nucleic Acids Res. 44, D457-D462 (2016).
Kanehisa, M. and Goto, S.; KEGG: Kyoto Encyclopedia of Genes and Genomes. Nucleic Acids Res. 28, 27-30 (2000).
Release files for bio2bel-kegg 0.3.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 | Actions |
|---|---|---|---|---|
| bio2bel_kegg-0.3.0.tar.gz | 25.1 kB | Without provenance | Details for bio2bel_kegg-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bio2bel_kegg-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for bio2bel_kegg-0.3.0-py3-none-any.whl |
Total release size: 38.8 kB
Release files / bio2bel_kegg-0.3.0.tar.gz
| Download URL | bio2bel_kegg-0.3.0.tar.gz |
|---|---|
| Size | 25.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fc59b2890ba9e2ee4c99a87c6a59d070fd8f1e1af4d5651c59ac4d125289b866
|
|
BLAKE2b-256 checksum How to use checksums |
8a367915e90c2c4331010f46aa246026b08aeb8a2e34ff00e0b7c2c26ce275a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.52.0 CPython/3.8.3
|
Release files / bio2bel_kegg-0.3.0-py3-none-any.whl
| Download URL | bio2bel_kegg-0.3.0-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c62a6fad7ae4c3de21b168728ca69d99b47cb8a409ddfe8a642c29101904a094
|
|
BLAKE2b-256 checksum How to use checksums |
172630e4a45b4e6da7c05e8c797aec6928a74700eee0ed55a28d2de3f729b318
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.52.0 CPython/3.8.3
|
Security for bio2bel-kegg 0.3.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.
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.
