BioClients 
Python package for access to online biomedical resources,
usually via REST APIs. Modules generally include
Client.py for command-line use and Utils.py for
integration into other code. With the advent of HTTP web services,
first SOAP/XML and then mostly REST/JSON, many online APIs
require very similar methods for data search, requests
and transforms into usable formats, often CSV/TSV.
Availability and installation
Source at https://github.com/jeremyjyang/BioClients;
releases available via pypi.org:
https://pypi.org/project/BioClients/
(pip3 install BioClients).
However, current development snapshot recommended.
(First download or clone.)
$ cd BioClients
$ python3 setup.py install
Dependencies
- Python 3.6+
- Python packages:
pandas,requests,urllib,json,xml,yaml,psycopg2,tqdm, etc.
Modules
AMP-T2D • BioGrid • BRENDA • Chem2Bio2RDF • ChEMBL • Disease Ontology • DisGeNet • DNorm • DrugCentral • EnsEMBL • FDA • Gene Ontology • GWAS Catalog • HUGO • HumanBase • iCite • IDG • JensenLab • LINCS • MaayanLab • MeSH • MONARCH • OMIM • Open Targets • Panther • PDB • PubChem • PubMed • PubTator • Reactome • RXNorm • STRINGDB • TCGA • TIN-X • UMLS • UniProt
Usage
$ python3 -m BioClients.pubchem.Client -h
Data structures and formats, XML, JSON, and CSV/TSV
BioClients is designed to be simple and practical, and XML, JSON and CSV/TSV are likewise simple in many respects, yet a great deal of conceptual and technological progress is reflected. XML and JSON can represent arbitrarily complex data objects, comprised of nested lists, dictionaries, and trees of primary types. CSV/TSV represents tables of rows and columns, related by common keys, reflecting the development of SQL and relational databases. Transforming JSON to CSV/TSV, as these clients generally do, projects data objects to tables useful for many applications (e.g. machine learning).
Metadata
Release files for bioclients 0.0.9
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 |
|---|---|---|---|---|
| BioClients-0.0.9.tar.gz | 133.7 kB | Without provenance | Details for BioClients-0.0.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| BioClients-0.0.9-py3-none-any.whl | Python 3 | none | any | Details for BioClients-0.0.9-py3-none-any.whl |
Total release size: 346.6 kB
Release files / BioClients-0.0.9.tar.gz
| Download URL | BioClients-0.0.9.tar.gz |
|---|---|
| Size | 133.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
77689945d8b5bc79570a2ac3fcbd570c2e26f58f2651c7e1d8d7ed156cdc8b62
|
|
BLAKE2b-256 checksum How to use checksums |
2796a54cfbfd071f22ca2f9bb4112e09ce48d4ca0738905ad1df67bd029cebc4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.6.9
|
Release files / BioClients-0.0.9-py3-none-any.whl
| Download URL | BioClients-0.0.9-py3-none-any.whl |
|---|---|
| Size | 212.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e4b9680b381a9eeb2b70530c2265d0a6701e66131479fa79a4170b8dc9d98b7
|
|
BLAKE2b-256 checksum How to use checksums |
7a24a069d89fdf8b7356c96bb09161abfeee3329e678871209a471abdca1f150
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.6.9
|
Security for bioclients 0.0.9
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.