| Name | pyobo JSON |
| Version |
0.11.1
JSON |
| download |
| home_page | None |
| Summary | A python package for handling and generating OBO |
| upload_time | 2024-11-05 08:04:07 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.9 |
| license | MIT License Copyright (c) 2024 Charles Tapley Hoyt Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
| keywords |
snekpack
cookiecutter
ontologies
biomedical ontologies
life sciences
natural sciences
bioinformatics
cheminformatics
open biomedical ontologies
obo
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
<!--
<p align="center">
<img src="https://github.com/biopragmatics/pyobo/raw/main/docs/source/logo.png" height="150">
</p>
-->
<h1 align="center">
PyOBO
</h1>
<p align="center">
<a href="https://github.com/biopragmatics/pyobo/actions/workflows/tests.yml">
<img alt="Tests" src="https://github.com/biopragmatics/pyobo/actions/workflows/tests.yml/badge.svg" /></a>
<a href="https://pypi.org/project/pyobo">
<img alt="PyPI" src="https://img.shields.io/pypi/v/pyobo" /></a>
<a href="https://pypi.org/project/pyobo">
<img alt="PyPI - Python Version" src="https://img.shields.io/pypi/pyversions/pyobo" /></a>
<a href="https://github.com/biopragmatics/pyobo/blob/main/LICENSE">
<img alt="PyPI - License" src="https://img.shields.io/pypi/l/pyobo" /></a>
<a href='https://pyobo.readthedocs.io/en/latest/?badge=latest'>
<img src='https://readthedocs.org/projects/pyobo/badge/?version=latest' alt='Documentation Status' /></a>
<a href="https://codecov.io/gh/biopragmatics/pyobo/branch/main">
<img src="https://codecov.io/gh/biopragmatics/pyobo/branch/main/graph/badge.svg" alt="Codecov status" /></a>
<a href="https://github.com/cthoyt/cookiecutter-python-package">
<img alt="Cookiecutter template from @cthoyt" src="https://img.shields.io/badge/Cookiecutter-snekpack-blue" /></a>
<a href="https://github.com/astral-sh/ruff">
<img src="https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json" alt="Ruff" style="max-width:100%;"></a>
<a href="https://github.com/biopragmatics/pyobo/blob/main/.github/CODE_OF_CONDUCT.md">
<img src="https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg" alt="Contributor Covenant"/></a>
<a href="https://doi.org/10.5281/zenodo.3381961">
<img src="https://zenodo.org/badge/DOI/10.5281/zenodo.3381961.svg" alt="DOI"></a>
</p>
Tools for biological identifiers, names, synonyms, xrefs, hierarchies, relations, and properties through the
perspective of OBO.
## Example Usage
Note! PyOBO is no-nonsense. This means that there's no repetitive
prefixes in identifiers. It also means all identifiers are strings,
no exceptions.
Note! The first time you run these, they have to download and cache
all resources. We're not in the business of redistributing data,
so all scripts should be completely reproducible. There's some
AWS tools for hosting/downloading pre-compiled versions in
`pyobo.aws` if you don't have time for that.
Note! PyOBO can perform grounding in a limited number of cases, but
it is *not* a general solution for named entity recognition (NER) or grounding.
It's suggested to check `Gilda <https://github.com/indralab/gilda>`_
for a no-nonsense solution.
### Mapping Identifiers and CURIEs
Get mapping of ChEBI identifiers to names:
```python
import pyobo
chebi_id_to_name = pyobo.get_id_name_mapping('chebi')
name = chebi_id_to_name['132964']
assert name == 'fluazifop-P-butyl'
```
Or, you don't have time for two lines:
```python
import pyobo
name = pyobo.get_name('chebi', '132964')
assert name == 'fluazifop-P-butyl'
```
Get reverse mapping of ChEBI names to identifiers:
```python
import pyobo
chebi_name_to_id = pyobo.get_name_id_mapping('chebi')
identifier = chebi_name_to_id['fluazifop-P-butyl']
assert identifier == '132964'
```
Maybe you live in CURIE world and just want to normalize something like
`CHEBI:132964`:
```python
import pyobo
name = pyobo.get_name_by_curie('CHEBI:132964')
assert name == 'fluazifop-P-butyl'
```
Sometimes you accidentally got an old CURIE. It can be mapped to the more recent
one using alternative identifiers listed in the underlying OBO with:
```python
import pyobo
# Look up DNA-binding transcription factor activity (go:0003700)
# based on an old id
primary_curie = pyobo.get_primary_curie('go:0001071')
assert primary_curie == 'go:0003700'
# If it's already the primary, it just gets returned
assert 'go:0003700' == pyobo.get_priority_curie('go:0003700')
```
### Mapping Species
Some resources have species information for their term. Get a mapping of WikiPathway identifiers
to species (as NCBI taxonomy identifiers):
```python
import pyobo
wikipathways_id_to_species = pyobo.get_id_species_mapping('wikipathways')
# Apoptosis (Homo sapiens)
taxonomy_id = wikipathways_id_to_species['WP254']
assert taxonomy_id == '9606'
```
Or, you don't have time for two lines:
```python
import pyobo
# Apoptosis (Homo sapiens)
taxonomy_id = pyobo.get_species('wikipathways', 'WP254')
assert taxonomy_id == '9606'
```
### Grounding
Maybe you've got names/synonyms you want to try and map back to ChEBI synonyms.
Given the brand name `Fusilade II` of `CHEBI:132964`, it should be able to look
it up and its preferred label.
```python
import pyobo
prefix, identifier, name = pyobo.ground('chebi', 'Fusilade II')
assert prefix == 'chebi'
assert identifier == '132964'
assert name == 'fluazifop-P-butyl'
# When failure happens...
prefix, identifier, name = pyobo.ground('chebi', 'Definitely not a real name')
assert prefix is None
assert identifier is None
assert name is None
```
If you're not really sure which namespace a name might belong to, you
can try a few in a row (prioritize by ones that cover the appropriate
entity type to avoid false positives in case of conflicts):
```python
import pyobo
# looking for phenotypes/pathways
prefix, identifier, name = pyobo.ground(['efo', 'go'], 'ERAD')
assert prefix == 'go'
assert identifier == '0030433'
assert name == 'ubiquitin-dependent ERAD pathway'
```
### Cross-referencing
Get xrefs from ChEBI to PubChem:
```python
import pyobo
chebi_id_to_pubchem_compound_id = pyobo.get_filtered_xrefs('chebi', 'pubchem.compound')
pubchem_compound_id = chebi_id_to_pubchem_compound_id['132964']
assert pubchem_compound_id == '3033674'
```
If you don't have time for two lines:
```python
import pyobo
pubchem_compound_id = pyobo.get_xref('chebi', '132964', 'pubchem.compound')
assert pubchem_compound_id == '3033674'
```
Get xrefs from Entrez to HGNC, but they're only available through HGNC,
so you need to flip them:
```python
import pyobo
hgnc_id_to_ncbigene_id = pyobo.get_filtered_xrefs('hgnc', 'ncbigene')
ncbigene_id_to_hgnc_id = {
ncbigene_id: hgnc_id
for hgnc_id, ncbigene_id in hgnc_id_to_ncbigene_id.items()
}
mapt_hgnc = ncbigene_id_to_hgnc_id['4137']
assert mapt_hgnc == '6893'
```
Since this is a common pattern, there's a keyword argument `flip`
that does this for you:
```python
import pyobo
ncbigene_id_to_hgnc_id = pyobo.get_filtered_xrefs('hgnc', 'ncbigene', flip=True)
mapt_hgnc_id = ncbigene_id_to_hgnc_id['4137']
assert mapt_hgnc_id == '6893'
```
If you don't have time for two lines (I admit this one is a bit confusing) and
need to flip it:
```python
import pyobo
hgnc_id = pyobo.get_xref('hgnc', '4137', 'ncbigene', flip=True)
assert hgnc_id == '6893'
```
Remap a CURIE based on pre-defined priority list and [Inspector Javert's Xref
Database](https://cthoyt.com/2020/04/19/inspector-javerts-xref-database.html):
```python
import pyobo
# Map to the best source possible
mapt_ncbigene = pyobo.get_priority_curie('hgnc:6893')
assert mapt_ncbigene == 'ncbigene:4137'
# Sometimes you know you're the best. Own it.
assert 'ncbigene:4137' == pyobo.get_priority_curie('ncbigene:4137')
```
Find all CURIEs mapped to a given one using Inspector Javert's Xref Database:
```python
import pyobo
# Get a set of all CURIEs mapped to MAPT
mapt_curies = pyobo.get_equivalent('hgnc:6893')
assert 'ncbigene:4137' in mapt_curies
assert 'ensembl:ENSG00000186868' in mapt_curies
```
If you don't want to wait to build the database locally for the `pyobo.get_priority_curie` and
`pyobo.get_equivalent`, you can use the following code to download a release from
[Zenodo](https://zenodo.org/record/3757266):
```python
import pyobo.resource_utils
pyobo.resource_utils.ensure_inspector_javert()
```
### Properties
Get properties, like SMILES. The semantics of these are defined on an OBO-OBO basis.
```python
import pyobo
# I don't make the rules. I wouldn't have chosen this as the key for this property. It could be any string
chebi_smiles_property = 'http://purl.obolibrary.org/obo/chebi/smiles'
chebi_id_to_smiles = pyobo.get_filtered_properties_mapping('chebi', chebi_smiles_property)
smiles = chebi_id_to_smiles['132964']
assert smiles == 'C1(=CC=C(N=C1)OC2=CC=C(C=C2)O[C@@H](C(OCCCC)=O)C)C(F)(F)F'
```
If you don't have time for two lines:
```python
import pyobo
smiles = pyobo.get_property('chebi', '132964', 'http://purl.obolibrary.org/obo/chebi/smiles')
assert smiles == 'C1(=CC=C(N=C1)OC2=CC=C(C=C2)O[C@@H](C(OCCCC)=O)C)C(F)(F)F'
```
### Hierarchy
Check if an entity is in the hierarchy:
```python
import networkx as nx
import pyobo
# check that go:0008219 ! cell death is an ancestor of go:0006915 ! apoptotic process
assert 'go:0008219' in pyobo.get_ancestors('go', '0006915')
# check that go:0070246 ! natural killer cell apoptotic process is a
# descendant of go:0006915 ! apoptotic process
apopototic_process_descendants = pyobo.get_descendants('go', '0006915')
assert 'go:0070246' in apopototic_process_descendants
```
Get the sub-hierarchy below a given node:
```python
import pyobo
# get the descendant graph of go:0006915 ! apoptotic process
apopototic_process_subhierarchy = pyobo.get_subhierarchy('go', '0006915')
# check that go:0070246 ! natural killer cell apoptotic process is a
# descendant of go:0006915 ! apoptotic process through the subhierarchy
assert 'go:0070246' in apopototic_process_subhierarchy
```
Get a hierarchy with properties preloaded in the node data dictionaries:
```python
import pyobo
prop = 'http://purl.obolibrary.org/obo/chebi/smiles'
chebi_hierarchy = pyobo.get_hierarchy('chebi', properties=[prop])
assert 'chebi:132964' in chebi_hierarchy
assert prop in chebi_hierarchy.nodes['chebi:132964']
assert chebi_hierarchy.nodes['chebi:132964'][prop] == 'C1(=CC=C(N=C1)OC2=CC=C(C=C2)O[C@@H](C(OCCCC)=O)C)C(F)(F)F'
```
### Relations
Get all orthologies (`ro:HOM0000017`) between HGNC and MGI (note: this is one way)
```python
>>> import pyobo
>>> human_mapt_hgnc_id = '6893'
>>> mouse_mapt_mgi_id = '97180'
>>> hgnc_mgi_orthology_mapping = pyobo.get_relation_mapping('hgnc', 'ro:HOM0000017', 'mgi')
>>> assert mouse_mapt_mgi_id == hgnc_mgi_orthology_mapping[human_mapt_hgnc_id]
```
If you want to do it in one line, use:
```python
>>> import pyobo
>>> human_mapt_hgnc_id = '6893'
>>> mouse_mapt_mgi_id = '97180'
>>> assert mouse_mapt_mgi_id == pyobo.get_relation('hgnc', 'ro:HOM0000017', 'mgi', human_mapt_hgnc_id)
```
### Writings Tests that Use PyOBO
If you're writing your own code that relies on PyOBO, and unit
testing it (as you should) in a continuous integration setting,
you've probably realized that loading all of the resources on each
build is not so fast. In those scenarios, you can use some of the
pre-build patches like in the following:
```python
import unittest
import pyobo
from pyobo.mocks import get_mock_id_name_mapping
mock_id_name_mapping = get_mock_id_name_mapping({
'chebi': {
'132964': 'fluazifop-P-butyl',
},
})
class MyTestCase(unittest.TestCase):
def my_test(self):
with mock_id_name_mapping:
# use functions directly, or use your functions that wrap them
pyobo.get_name('chebi', '1234')
```
## Curation of the Bioregistry
In order to normalize references and identify resources, PyOBO uses the
[Bioregistry](https://github.com/bioregistry/bioregistry). It used to be a part of PyOBO, but has since
been externalized for more general reuse.
At [src/pyobo/registries/metaregistry.json](https://github.com/pyobo/pyobo/blob/master/src/pyobo/registries/metaregistry.json)
is the curated "metaregistry". This is a source of information that contains
all sorts of fixes for missing/wrong information in MIRIAM, OLS, and OBO Foundry; entries that don't appear in
any of them; additional synonym information for each namespace/prefix; rules for normalizing xrefs and CURIEs, etc.
Other entries in the metaregistry:
- The `"remappings"->"full"` entry is a dictionary from strings that might follow `xref:`
in a given OBO file that need to be completely replaced, due to incorrect formatting
- The `"remappings"->"prefix"` entry contains a dictionary of prefixes for xrefs that need
to be remapped. Several rules, for example, remove superfluous spaces that occur inside
CURIEs or and others address instances of the GOGO issue.
- The `"blacklists"` entry contains rules for throwing out malformed xrefs based on
full string, just prefix, or just suffix.
## Troubleshooting
The OBO Foundry seems to be pretty unstable with respect to the URLs to OBO resources. If you get an error like:
```
pyobo.getters.MissingOboBuild: OBO Foundry is missing a build for: mondo
```
Then you should check the corresponding page on the OBO Foundry (in this case, http://www.obofoundry.org/ontology/mondo.html)
and make update to the `url` entry for that namespace in the Bioregistry.
## 🚀 Installation
The most recent release can be installed from
[PyPI](https://pypi.org/project/pyobo/) with:
```console
python3 -m pip install pyobo
```
The most recent code and data can be installed directly from GitHub with:
```console
python3 -m pip install git+https://github.com/biopragmatics/pyobo.git
```
## 👐 Contributing
Contributions, whether filing an issue, making a pull request, or forking, are appreciated. See
[CONTRIBUTING.md](https://github.com/biopragmatics/pyobo/blob/master/.github/CONTRIBUTING.md)
for more information on getting involved.
## 👋 Attribution
### ⚖️ License
The code in this package is licensed under the MIT License.
<!--
### 📖 Citation
Citation goes here!
-->
<!--
### 🎁 Support
This project has been supported by the following organizations (in alphabetical order):
- [Biopragmatics Lab](https://biopragmatics.github.io)
-->
<!--
### 💰 Funding
This project has been supported by the following grants:
| Funding Body | Program | Grant Number |
|---------------|--------------------------------------------------------------|--------------|
| Funder | [Grant Name (GRANT-ACRONYM)](https://example.com/grant-link) | ABCXYZ |
-->
### 🍪 Cookiecutter
This package was created with [@audreyfeldroy](https://github.com/audreyfeldroy)'s
[cookiecutter](https://github.com/cookiecutter/cookiecutter) package using [@cthoyt](https://github.com/cthoyt)'s
[cookiecutter-snekpack](https://github.com/cthoyt/cookiecutter-snekpack) template.
## 🛠️ For Developers
<details>
<summary>See developer instructions</summary>
The final section of the README is for if you want to get involved by making a code contribution.
### Development Installation
To install in development mode, use the following:
```console
git clone git+https://github.com/biopragmatics/pyobo.git
cd pyobo
python3 -m pip install -e .
```
### Updating Package Boilerplate
This project uses `cruft` to keep boilerplate (i.e., configuration, contribution guidelines, documentation
configuration)
up-to-date with the upstream cookiecutter package. Update with the following:
```console
python3 -m pip install cruft
cruft update
```
More info on Cruft's update command is
available [here](https://github.com/cruft/cruft?tab=readme-ov-file#updating-a-project).
### 🥼 Testing
After cloning the repository and installing `tox` with
`python3 -m pip install tox tox-uv`,
the unit tests in the `tests/` folder can be run reproducibly with:
```console
tox -e py
```
Additionally, these tests are automatically re-run with each commit in a
[GitHub Action](https://github.com/biopragmatics/pyobo/actions?query=workflow%3ATests).
### 📖 Building the Documentation
The documentation can be built locally using the following:
```console
git clone git+https://github.com/biopragmatics/pyobo.git
cd pyobo
tox -e docs
open docs/build/html/index.html
```
The documentation automatically installs the package as well as the `docs`
extra specified in the [`pyproject.toml`](../../Desktop/pyobo/pyproject.toml). `sphinx` plugins
like `texext` can be added there. Additionally, they need to be added to the
`extensions` list in [`docs/source/conf.py`](../../Desktop/pyobo/docs/source/conf.py).
The documentation can be deployed to [ReadTheDocs](https://readthedocs.io) using
[this guide](https://docs.readthedocs.io/en/stable/intro/import-guide.html).
The [`.readthedocs.yml`](../../Desktop/pyobo/.readthedocs.yml) YAML file contains all the configuration you'll need.
You can also set up continuous integration on GitHub to check not only that
Sphinx can build the documentation in an isolated environment (i.e., with `tox -e docs-test`)
but also that [ReadTheDocs can build it too](https://docs.readthedocs.io/en/stable/pull-requests.html).
#### Configuring ReadTheDocs
1. Log in to ReadTheDocs with your GitHub account to install the integration
at https://readthedocs.org/accounts/login/?next=/dashboard/
2. Import your project by navigating to https://readthedocs.org/dashboard/import then clicking the plus icon next to
your repository
3. You can rename the repository on the next screen using a more stylized name (i.e., with spaces and capital letters)
4. Click next, and you're good to go!
### 📦 Making a Release
#### Configuring Zenodo
[Zenodo](https://zenodo.org) is a long-term archival system that assigns a DOI to each release of your package.
1. Log in to Zenodo via GitHub with this link: https://zenodo.org/oauth/login/github/?next=%2F. This brings you to a
page that lists all of your organizations and asks you to approve installing the Zenodo app on GitHub. Click "grant"
next to any organizations you want to enable the integration for, then click the big green "approve" button. This
step only needs to be done once.
2. Navigate to https://zenodo.org/account/settings/github/, which lists all of your GitHub repositories (both in your
username and any organizations you enabled). Click the on/off toggle for any relevant repositories. When you make
a new repository, you'll have to come back to this
After these steps, you're ready to go! After you make "release" on GitHub (steps for this are below), you can navigate
to https://zenodo.org/account/settings/github/repository/biopragmatics/pyobo
to see the DOI for the release and link to the Zenodo record for it.
#### Registering with the Python Package Index (PyPI)
You only have to do the following steps once.
1. Register for an account on the [Python Package Index (PyPI)](https://pypi.org/account/register)
2. Navigate to https://pypi.org/manage/account and make sure you have verified your email address. A verification email
might not have been sent by default, so you might have to click the "options" dropdown next to your address to get to
the "re-send verification email" button
3. 2-Factor authentication is required for PyPI since the end of 2023 (see
this [blog post from PyPI](https://blog.pypi.org/posts/2023-05-25-securing-pypi-with-2fa/)). This means
you have to first issue account recovery codes, then set up 2-factor authentication
4. Issue an API token from https://pypi.org/manage/account/token
#### Configuring your machine's connection to PyPI
You have to do the following steps once per machine.
```console
$ uv tool install keyring
$ keyring set https://upload.pypi.org/legacy/ __token__
$ keyring set https://test.pypi.org/legacy/ __token__
```
Note that this deprecates previous workflows using `.pypirc`.
#### Uploading to PyPI
After installing the package in development mode and installing
`tox` with `python3 -m pip install tox tox-uv`,
run the following from the console:
```console
tox -e finish
```
This script does the following:
1. Uses [bump-my-version](https://github.com/callowayproject/bump-my-version) to switch the version number in
the `pyproject.toml`, `CITATION.cff`, `src/pyobo/version.py`,
and [`docs/source/conf.py`](../../Desktop/pyobo/docs/source/conf.py) to not have the `-dev` suffix
2. Packages the code in both a tar archive and a wheel using
[`uv build`](https://docs.astral.sh/uv/guides/publish/#building-your-package)
3. Uploads to PyPI using [`uv publish`](https://docs.astral.sh/uv/guides/publish/#publishing-your-package).
4. Push to GitHub. You'll need to make a release going with the commit where the version was bumped.
5. Bump the version to the next patch. If you made big changes and want to bump the version by minor, you can
use `tox -e bumpversion -- minor` after.
#### Releasing on GitHub
1. Navigate
to https://github.com/biopragmatics/pyobo/releases/new
to draft a new release
2. Click the "Choose a Tag" dropdown and select the tag corresponding to the release you just made
3. Click the "Generate Release Notes" button to get a quick outline of recent changes. Modify the title and description
as you see fit
4. Click the big green "Publish Release" button
This will trigger Zenodo to assign a DOI to your release as well.
</details>
Raw data
{
"_id": null,
"home_page": null,
"name": "pyobo",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.9",
"maintainer_email": "Charles Tapley Hoyt <cthoyt@gmail.com>",
"keywords": "snekpack, cookiecutter, ontologies, biomedical ontologies, life sciences, natural sciences, bioinformatics, cheminformatics, Open Biomedical Ontologies, OBO",
"author": null,
"author_email": "Charles Tapley Hoyt <cthoyt@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/78/49/f96e3172d21d3749611cbbcab4e39cf70755885b70ab1406ebef7c414902/pyobo-0.11.1.tar.gz",
"platform": null,
"description": "<!--\n<p align=\"center\">\n <img src=\"https://github.com/biopragmatics/pyobo/raw/main/docs/source/logo.png\" height=\"150\">\n</p>\n-->\n\n<h1 align=\"center\">\n PyOBO\n</h1>\n\n<p align=\"center\">\n <a href=\"https://github.com/biopragmatics/pyobo/actions/workflows/tests.yml\">\n <img alt=\"Tests\" src=\"https://github.com/biopragmatics/pyobo/actions/workflows/tests.yml/badge.svg\" /></a>\n <a href=\"https://pypi.org/project/pyobo\">\n <img alt=\"PyPI\" src=\"https://img.shields.io/pypi/v/pyobo\" /></a>\n <a href=\"https://pypi.org/project/pyobo\">\n <img alt=\"PyPI - Python Version\" src=\"https://img.shields.io/pypi/pyversions/pyobo\" /></a>\n <a href=\"https://github.com/biopragmatics/pyobo/blob/main/LICENSE\">\n <img alt=\"PyPI - License\" src=\"https://img.shields.io/pypi/l/pyobo\" /></a>\n <a href='https://pyobo.readthedocs.io/en/latest/?badge=latest'>\n <img src='https://readthedocs.org/projects/pyobo/badge/?version=latest' alt='Documentation Status' /></a>\n <a href=\"https://codecov.io/gh/biopragmatics/pyobo/branch/main\">\n <img src=\"https://codecov.io/gh/biopragmatics/pyobo/branch/main/graph/badge.svg\" alt=\"Codecov status\" /></a> \n <a href=\"https://github.com/cthoyt/cookiecutter-python-package\">\n <img alt=\"Cookiecutter template from @cthoyt\" src=\"https://img.shields.io/badge/Cookiecutter-snekpack-blue\" /></a>\n <a href=\"https://github.com/astral-sh/ruff\">\n <img src=\"https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json\" alt=\"Ruff\" style=\"max-width:100%;\"></a>\n <a href=\"https://github.com/biopragmatics/pyobo/blob/main/.github/CODE_OF_CONDUCT.md\">\n <img src=\"https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg\" alt=\"Contributor Covenant\"/></a>\n <a href=\"https://doi.org/10.5281/zenodo.3381961\">\n <img src=\"https://zenodo.org/badge/DOI/10.5281/zenodo.3381961.svg\" alt=\"DOI\"></a>\n</p>\n\nTools for biological identifiers, names, synonyms, xrefs, hierarchies, relations, and properties through the\nperspective of OBO.\n\n## Example Usage\n\nNote! PyOBO is no-nonsense. This means that there's no repetitive\nprefixes in identifiers. It also means all identifiers are strings,\nno exceptions.\n\nNote! The first time you run these, they have to download and cache\nall resources. We're not in the business of redistributing data,\nso all scripts should be completely reproducible. There's some\nAWS tools for hosting/downloading pre-compiled versions in\n`pyobo.aws` if you don't have time for that.\n\nNote! PyOBO can perform grounding in a limited number of cases, but\nit is *not* a general solution for named entity recognition (NER) or grounding.\nIt's suggested to check `Gilda <https://github.com/indralab/gilda>`_\nfor a no-nonsense solution.\n\n### Mapping Identifiers and CURIEs\n\nGet mapping of ChEBI identifiers to names:\n\n```python\nimport pyobo\n\nchebi_id_to_name = pyobo.get_id_name_mapping('chebi')\n\nname = chebi_id_to_name['132964']\nassert name == 'fluazifop-P-butyl'\n```\n\nOr, you don't have time for two lines:\n\n```python\nimport pyobo\n\nname = pyobo.get_name('chebi', '132964')\nassert name == 'fluazifop-P-butyl'\n```\n\nGet reverse mapping of ChEBI names to identifiers:\n\n```python\nimport pyobo\n\nchebi_name_to_id = pyobo.get_name_id_mapping('chebi')\n\nidentifier = chebi_name_to_id['fluazifop-P-butyl']\nassert identifier == '132964'\n```\n\nMaybe you live in CURIE world and just want to normalize something like\n`CHEBI:132964`:\n\n```python\nimport pyobo\n\nname = pyobo.get_name_by_curie('CHEBI:132964')\nassert name == 'fluazifop-P-butyl'\n```\n\nSometimes you accidentally got an old CURIE. It can be mapped to the more recent\none using alternative identifiers listed in the underlying OBO with:\n\n```python\nimport pyobo\n\n# Look up DNA-binding transcription factor activity (go:0003700)\n# based on an old id\nprimary_curie = pyobo.get_primary_curie('go:0001071')\nassert primary_curie == 'go:0003700'\n\n# If it's already the primary, it just gets returned\nassert 'go:0003700' == pyobo.get_priority_curie('go:0003700')\n```\n\n### Mapping Species\n\nSome resources have species information for their term. Get a mapping of WikiPathway identifiers\nto species (as NCBI taxonomy identifiers):\n\n```python\nimport pyobo\n\nwikipathways_id_to_species = pyobo.get_id_species_mapping('wikipathways')\n\n# Apoptosis (Homo sapiens)\ntaxonomy_id = wikipathways_id_to_species['WP254']\nassert taxonomy_id == '9606'\n```\n\nOr, you don't have time for two lines:\n\n```python\nimport pyobo\n\n# Apoptosis (Homo sapiens)\ntaxonomy_id = pyobo.get_species('wikipathways', 'WP254')\nassert taxonomy_id == '9606'\n```\n\n### Grounding\n\nMaybe you've got names/synonyms you want to try and map back to ChEBI synonyms.\nGiven the brand name `Fusilade II` of `CHEBI:132964`, it should be able to look\nit up and its preferred label.\n\n```python\nimport pyobo\n\nprefix, identifier, name = pyobo.ground('chebi', 'Fusilade II')\nassert prefix == 'chebi'\nassert identifier == '132964'\nassert name == 'fluazifop-P-butyl'\n\n# When failure happens...\nprefix, identifier, name = pyobo.ground('chebi', 'Definitely not a real name')\nassert prefix is None\nassert identifier is None\nassert name is None\n```\n\nIf you're not really sure which namespace a name might belong to, you\ncan try a few in a row (prioritize by ones that cover the appropriate\nentity type to avoid false positives in case of conflicts):\n\n```python\nimport pyobo\n\n# looking for phenotypes/pathways\nprefix, identifier, name = pyobo.ground(['efo', 'go'], 'ERAD')\nassert prefix == 'go'\nassert identifier == '0030433'\nassert name == 'ubiquitin-dependent ERAD pathway'\n```\n\n### Cross-referencing\n\nGet xrefs from ChEBI to PubChem:\n\n```python\nimport pyobo\n\nchebi_id_to_pubchem_compound_id = pyobo.get_filtered_xrefs('chebi', 'pubchem.compound')\n\npubchem_compound_id = chebi_id_to_pubchem_compound_id['132964']\nassert pubchem_compound_id == '3033674'\n```\n\nIf you don't have time for two lines:\n\n```python\nimport pyobo\n\npubchem_compound_id = pyobo.get_xref('chebi', '132964', 'pubchem.compound')\nassert pubchem_compound_id == '3033674'\n```\n\nGet xrefs from Entrez to HGNC, but they're only available through HGNC,\nso you need to flip them:\n\n```python\nimport pyobo\n\nhgnc_id_to_ncbigene_id = pyobo.get_filtered_xrefs('hgnc', 'ncbigene')\nncbigene_id_to_hgnc_id = {\n ncbigene_id: hgnc_id\n for hgnc_id, ncbigene_id in hgnc_id_to_ncbigene_id.items()\n}\nmapt_hgnc = ncbigene_id_to_hgnc_id['4137']\nassert mapt_hgnc == '6893'\n```\n\nSince this is a common pattern, there's a keyword argument `flip`\nthat does this for you:\n\n```python\nimport pyobo\n\nncbigene_id_to_hgnc_id = pyobo.get_filtered_xrefs('hgnc', 'ncbigene', flip=True)\nmapt_hgnc_id = ncbigene_id_to_hgnc_id['4137']\nassert mapt_hgnc_id == '6893'\n```\n\nIf you don't have time for two lines (I admit this one is a bit confusing) and\nneed to flip it:\n\n```python\nimport pyobo\n\nhgnc_id = pyobo.get_xref('hgnc', '4137', 'ncbigene', flip=True)\nassert hgnc_id == '6893'\n```\n\nRemap a CURIE based on pre-defined priority list and [Inspector Javert's Xref\nDatabase](https://cthoyt.com/2020/04/19/inspector-javerts-xref-database.html):\n\n```python\n\nimport pyobo\n\n# Map to the best source possible\nmapt_ncbigene = pyobo.get_priority_curie('hgnc:6893')\nassert mapt_ncbigene == 'ncbigene:4137'\n\n# Sometimes you know you're the best. Own it.\nassert 'ncbigene:4137' == pyobo.get_priority_curie('ncbigene:4137')\n```\n\nFind all CURIEs mapped to a given one using Inspector Javert's Xref Database:\n\n```python\nimport pyobo\n\n# Get a set of all CURIEs mapped to MAPT\nmapt_curies = pyobo.get_equivalent('hgnc:6893')\nassert 'ncbigene:4137' in mapt_curies\nassert 'ensembl:ENSG00000186868' in mapt_curies\n```\n\nIf you don't want to wait to build the database locally for the `pyobo.get_priority_curie` and\n`pyobo.get_equivalent`, you can use the following code to download a release from\n[Zenodo](https://zenodo.org/record/3757266):\n\n```python\nimport pyobo.resource_utils\n\npyobo.resource_utils.ensure_inspector_javert()\n```\n\n### Properties\n\nGet properties, like SMILES. The semantics of these are defined on an OBO-OBO basis.\n\n```python\nimport pyobo\n\n# I don't make the rules. I wouldn't have chosen this as the key for this property. It could be any string\nchebi_smiles_property = 'http://purl.obolibrary.org/obo/chebi/smiles'\nchebi_id_to_smiles = pyobo.get_filtered_properties_mapping('chebi', chebi_smiles_property)\n\nsmiles = chebi_id_to_smiles['132964']\nassert smiles == 'C1(=CC=C(N=C1)OC2=CC=C(C=C2)O[C@@H](C(OCCCC)=O)C)C(F)(F)F'\n```\n\nIf you don't have time for two lines:\n\n```python\nimport pyobo\n\nsmiles = pyobo.get_property('chebi', '132964', 'http://purl.obolibrary.org/obo/chebi/smiles')\nassert smiles == 'C1(=CC=C(N=C1)OC2=CC=C(C=C2)O[C@@H](C(OCCCC)=O)C)C(F)(F)F'\n```\n\n### Hierarchy\n\nCheck if an entity is in the hierarchy:\n\n```python\nimport networkx as nx\nimport pyobo\n\n# check that go:0008219 ! cell death is an ancestor of go:0006915 ! apoptotic process\nassert 'go:0008219' in pyobo.get_ancestors('go', '0006915')\n\n# check that go:0070246 ! natural killer cell apoptotic process is a\n# descendant of go:0006915 ! apoptotic process\napopototic_process_descendants = pyobo.get_descendants('go', '0006915')\nassert 'go:0070246' in apopototic_process_descendants\n```\n\nGet the sub-hierarchy below a given node:\n\n```python\nimport pyobo\n\n# get the descendant graph of go:0006915 ! apoptotic process\napopototic_process_subhierarchy = pyobo.get_subhierarchy('go', '0006915')\n\n# check that go:0070246 ! natural killer cell apoptotic process is a\n# descendant of go:0006915 ! apoptotic process through the subhierarchy\nassert 'go:0070246' in apopototic_process_subhierarchy\n```\n\nGet a hierarchy with properties preloaded in the node data dictionaries:\n\n```python\nimport pyobo\n\nprop = 'http://purl.obolibrary.org/obo/chebi/smiles'\nchebi_hierarchy = pyobo.get_hierarchy('chebi', properties=[prop])\n\nassert 'chebi:132964' in chebi_hierarchy\nassert prop in chebi_hierarchy.nodes['chebi:132964']\nassert chebi_hierarchy.nodes['chebi:132964'][prop] == 'C1(=CC=C(N=C1)OC2=CC=C(C=C2)O[C@@H](C(OCCCC)=O)C)C(F)(F)F'\n```\n\n### Relations\n\nGet all orthologies (`ro:HOM0000017`) between HGNC and MGI (note: this is one way)\n\n```python\n>>> import pyobo\n>>> human_mapt_hgnc_id = '6893'\n>>> mouse_mapt_mgi_id = '97180'\n>>> hgnc_mgi_orthology_mapping = pyobo.get_relation_mapping('hgnc', 'ro:HOM0000017', 'mgi')\n>>> assert mouse_mapt_mgi_id == hgnc_mgi_orthology_mapping[human_mapt_hgnc_id]\n```\n\nIf you want to do it in one line, use:\n\n```python\n\n>>> import pyobo\n>>> human_mapt_hgnc_id = '6893'\n>>> mouse_mapt_mgi_id = '97180'\n>>> assert mouse_mapt_mgi_id == pyobo.get_relation('hgnc', 'ro:HOM0000017', 'mgi', human_mapt_hgnc_id)\n```\n\n### Writings Tests that Use PyOBO\n\nIf you're writing your own code that relies on PyOBO, and unit\ntesting it (as you should) in a continuous integration setting,\nyou've probably realized that loading all of the resources on each\nbuild is not so fast. In those scenarios, you can use some of the\npre-build patches like in the following:\n\n```python\nimport unittest\nimport pyobo\nfrom pyobo.mocks import get_mock_id_name_mapping\n\nmock_id_name_mapping = get_mock_id_name_mapping({\n 'chebi': {\n '132964': 'fluazifop-P-butyl',\n },\n})\n\nclass MyTestCase(unittest.TestCase):\n def my_test(self):\n with mock_id_name_mapping:\n # use functions directly, or use your functions that wrap them\n pyobo.get_name('chebi', '1234')\n```\n\n\n## Curation of the Bioregistry\n\nIn order to normalize references and identify resources, PyOBO uses the\n[Bioregistry](https://github.com/bioregistry/bioregistry). It used to be a part of PyOBO, but has since\nbeen externalized for more general reuse.\n\nAt [src/pyobo/registries/metaregistry.json](https://github.com/pyobo/pyobo/blob/master/src/pyobo/registries/metaregistry.json)\nis the curated \"metaregistry\". This is a source of information that contains\nall sorts of fixes for missing/wrong information in MIRIAM, OLS, and OBO Foundry; entries that don't appear in\nany of them; additional synonym information for each namespace/prefix; rules for normalizing xrefs and CURIEs, etc.\n\nOther entries in the metaregistry:\n\n- The `\"remappings\"->\"full\"` entry is a dictionary from strings that might follow `xref:`\n in a given OBO file that need to be completely replaced, due to incorrect formatting\n- The `\"remappings\"->\"prefix\"` entry contains a dictionary of prefixes for xrefs that need\n to be remapped. Several rules, for example, remove superfluous spaces that occur inside\n CURIEs or and others address instances of the GOGO issue.\n- The `\"blacklists\"` entry contains rules for throwing out malformed xrefs based on\n full string, just prefix, or just suffix.\n\n## Troubleshooting\n\nThe OBO Foundry seems to be pretty unstable with respect to the URLs to OBO resources. If you get an error like:\n\n```\npyobo.getters.MissingOboBuild: OBO Foundry is missing a build for: mondo\n```\n\nThen you should check the corresponding page on the OBO Foundry (in this case, http://www.obofoundry.org/ontology/mondo.html)\nand make update to the `url` entry for that namespace in the Bioregistry.\n\n## \ud83d\ude80 Installation\n\nThe most recent release can be installed from\n[PyPI](https://pypi.org/project/pyobo/) with:\n\n```console\npython3 -m pip install pyobo\n```\n\nThe most recent code and data can be installed directly from GitHub with:\n\n```console\npython3 -m pip install git+https://github.com/biopragmatics/pyobo.git\n```\n\n## \ud83d\udc50 Contributing\n\nContributions, whether filing an issue, making a pull request, or forking, are appreciated. See\n[CONTRIBUTING.md](https://github.com/biopragmatics/pyobo/blob/master/.github/CONTRIBUTING.md)\nfor more information on getting involved.\n\n## \ud83d\udc4b Attribution\n\n### \u2696\ufe0f License\n\nThe code in this package is licensed under the MIT License.\n\n<!--\n### \ud83d\udcd6 Citation\n\nCitation goes here!\n-->\n\n<!--\n### \ud83c\udf81 Support\n\nThis project has been supported by the following organizations (in alphabetical order):\n\n- [Biopragmatics Lab](https://biopragmatics.github.io)\n\n-->\n\n<!--\n### \ud83d\udcb0 Funding\n\nThis project has been supported by the following grants:\n\n| Funding Body | Program | Grant Number |\n|---------------|--------------------------------------------------------------|--------------|\n| Funder | [Grant Name (GRANT-ACRONYM)](https://example.com/grant-link) | ABCXYZ |\n-->\n\n### \ud83c\udf6a Cookiecutter\n\nThis package was created with [@audreyfeldroy](https://github.com/audreyfeldroy)'s\n[cookiecutter](https://github.com/cookiecutter/cookiecutter) package using [@cthoyt](https://github.com/cthoyt)'s\n[cookiecutter-snekpack](https://github.com/cthoyt/cookiecutter-snekpack) template.\n\n## \ud83d\udee0\ufe0f For Developers\n\n<details>\n <summary>See developer instructions</summary>\n\nThe final section of the README is for if you want to get involved by making a code contribution.\n\n### Development Installation\n\nTo install in development mode, use the following:\n\n```console\ngit clone git+https://github.com/biopragmatics/pyobo.git\ncd pyobo\npython3 -m pip install -e .\n```\n\n### Updating Package Boilerplate\n\nThis project uses `cruft` to keep boilerplate (i.e., configuration, contribution guidelines, documentation\nconfiguration)\nup-to-date with the upstream cookiecutter package. Update with the following:\n\n```console\npython3 -m pip install cruft\ncruft update\n```\n\nMore info on Cruft's update command is\navailable [here](https://github.com/cruft/cruft?tab=readme-ov-file#updating-a-project).\n\n### \ud83e\udd7c Testing\n\nAfter cloning the repository and installing `tox` with\n`python3 -m pip install tox tox-uv`,\nthe unit tests in the `tests/` folder can be run reproducibly with:\n\n```console\ntox -e py\n```\n\nAdditionally, these tests are automatically re-run with each commit in a\n[GitHub Action](https://github.com/biopragmatics/pyobo/actions?query=workflow%3ATests).\n\n### \ud83d\udcd6 Building the Documentation\n\nThe documentation can be built locally using the following:\n\n```console\ngit clone git+https://github.com/biopragmatics/pyobo.git\ncd pyobo\ntox -e docs\nopen docs/build/html/index.html\n```\n\nThe documentation automatically installs the package as well as the `docs`\nextra specified in the [`pyproject.toml`](../../Desktop/pyobo/pyproject.toml). `sphinx` plugins\nlike `texext` can be added there. Additionally, they need to be added to the\n`extensions` list in [`docs/source/conf.py`](../../Desktop/pyobo/docs/source/conf.py).\n\nThe documentation can be deployed to [ReadTheDocs](https://readthedocs.io) using\n[this guide](https://docs.readthedocs.io/en/stable/intro/import-guide.html).\nThe [`.readthedocs.yml`](../../Desktop/pyobo/.readthedocs.yml) YAML file contains all the configuration you'll need.\nYou can also set up continuous integration on GitHub to check not only that\nSphinx can build the documentation in an isolated environment (i.e., with `tox -e docs-test`)\nbut also that [ReadTheDocs can build it too](https://docs.readthedocs.io/en/stable/pull-requests.html).\n\n#### Configuring ReadTheDocs\n\n1. Log in to ReadTheDocs with your GitHub account to install the integration\n at https://readthedocs.org/accounts/login/?next=/dashboard/\n2. Import your project by navigating to https://readthedocs.org/dashboard/import then clicking the plus icon next to\n your repository\n3. You can rename the repository on the next screen using a more stylized name (i.e., with spaces and capital letters)\n4. Click next, and you're good to go!\n\n### \ud83d\udce6 Making a Release\n\n#### Configuring Zenodo\n\n[Zenodo](https://zenodo.org) is a long-term archival system that assigns a DOI to each release of your package.\n\n1. Log in to Zenodo via GitHub with this link: https://zenodo.org/oauth/login/github/?next=%2F. This brings you to a\n page that lists all of your organizations and asks you to approve installing the Zenodo app on GitHub. Click \"grant\"\n next to any organizations you want to enable the integration for, then click the big green \"approve\" button. This\n step only needs to be done once.\n2. Navigate to https://zenodo.org/account/settings/github/, which lists all of your GitHub repositories (both in your\n username and any organizations you enabled). Click the on/off toggle for any relevant repositories. When you make\n a new repository, you'll have to come back to this\n\nAfter these steps, you're ready to go! After you make \"release\" on GitHub (steps for this are below), you can navigate\nto https://zenodo.org/account/settings/github/repository/biopragmatics/pyobo\nto see the DOI for the release and link to the Zenodo record for it.\n\n#### Registering with the Python Package Index (PyPI)\n\nYou only have to do the following steps once.\n\n1. Register for an account on the [Python Package Index (PyPI)](https://pypi.org/account/register)\n2. Navigate to https://pypi.org/manage/account and make sure you have verified your email address. A verification email\n might not have been sent by default, so you might have to click the \"options\" dropdown next to your address to get to\n the \"re-send verification email\" button\n3. 2-Factor authentication is required for PyPI since the end of 2023 (see\n this [blog post from PyPI](https://blog.pypi.org/posts/2023-05-25-securing-pypi-with-2fa/)). This means\n you have to first issue account recovery codes, then set up 2-factor authentication\n4. Issue an API token from https://pypi.org/manage/account/token\n\n#### Configuring your machine's connection to PyPI\n\nYou have to do the following steps once per machine. \n\n```console\n$ uv tool install keyring\n$ keyring set https://upload.pypi.org/legacy/ __token__\n$ keyring set https://test.pypi.org/legacy/ __token__\n```\n\nNote that this deprecates previous workflows using `.pypirc`.\n\n#### Uploading to PyPI\n\nAfter installing the package in development mode and installing\n`tox` with `python3 -m pip install tox tox-uv`,\nrun the following from the console:\n\n```console\ntox -e finish\n```\n\nThis script does the following:\n\n1. Uses [bump-my-version](https://github.com/callowayproject/bump-my-version) to switch the version number in\n the `pyproject.toml`, `CITATION.cff`, `src/pyobo/version.py`,\n and [`docs/source/conf.py`](../../Desktop/pyobo/docs/source/conf.py) to not have the `-dev` suffix\n2. Packages the code in both a tar archive and a wheel using\n [`uv build`](https://docs.astral.sh/uv/guides/publish/#building-your-package)\n3. Uploads to PyPI using [`uv publish`](https://docs.astral.sh/uv/guides/publish/#publishing-your-package).\n4. Push to GitHub. You'll need to make a release going with the commit where the version was bumped.\n5. Bump the version to the next patch. If you made big changes and want to bump the version by minor, you can\n use `tox -e bumpversion -- minor` after.\n\n#### Releasing on GitHub\n\n1. Navigate\n to https://github.com/biopragmatics/pyobo/releases/new\n to draft a new release\n2. Click the \"Choose a Tag\" dropdown and select the tag corresponding to the release you just made\n3. Click the \"Generate Release Notes\" button to get a quick outline of recent changes. Modify the title and description\n as you see fit\n4. Click the big green \"Publish Release\" button\n\nThis will trigger Zenodo to assign a DOI to your release as well.\n\n</details>\n",
"bugtrack_url": null,
"license": "MIT License Copyright (c) 2024 Charles Tapley Hoyt Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ",
"summary": "A python package for handling and generating OBO",
"version": "0.11.1",
"project_urls": {
"Bug Tracker": "https://github.com/biopragmatics/pyobo/issues",
"Documentation": "https://pyobo.readthedocs.io",
"Homepage": "https://github.com/biopragmatics/pyobo",
"Repository": "https://github.com/biopragmatics/pyobo.git"
},
"split_keywords": [
"snekpack",
" cookiecutter",
" ontologies",
" biomedical ontologies",
" life sciences",
" natural sciences",
" bioinformatics",
" cheminformatics",
" open biomedical ontologies",
" obo"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "9eb6a51860a34d5f628baf0cf90171953e7b241e6235191f2d7a37e66bacd5f3",
"md5": "171636b4d35e7e35fc85a88bc05e238b",
"sha256": "4c741488fb4eba7de9546fffc4cb6fa3e94ad786c3fff67697bfca333c67d659"
},
"downloads": -1,
"filename": "pyobo-0.11.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "171636b4d35e7e35fc85a88bc05e238b",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9",
"size": 23131107,
"upload_time": "2024-11-05T08:03:58",
"upload_time_iso_8601": "2024-11-05T08:03:58.457879Z",
"url": "https://files.pythonhosted.org/packages/9e/b6/a51860a34d5f628baf0cf90171953e7b241e6235191f2d7a37e66bacd5f3/pyobo-0.11.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "7849f96e3172d21d3749611cbbcab4e39cf70755885b70ab1406ebef7c414902",
"md5": "9c14a1be7513bac6e2a63396de066937",
"sha256": "0a022e1528fe69b8b5bf5cbc07cfd0ceaf42b400d2c31a6c9d0d3c912335459e"
},
"downloads": -1,
"filename": "pyobo-0.11.1.tar.gz",
"has_sig": false,
"md5_digest": "9c14a1be7513bac6e2a63396de066937",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9",
"size": 23081174,
"upload_time": "2024-11-05T08:04:07",
"upload_time_iso_8601": "2024-11-05T08:04:07.357257Z",
"url": "https://files.pythonhosted.org/packages/78/49/f96e3172d21d3749611cbbcab4e39cf70755885b70ab1406ebef7c414902/pyobo-0.11.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-11-05 08:04:07",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "biopragmatics",
"github_project": "pyobo",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"tox": true,
"lcname": "pyobo"
}
