Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/biopragmatics/bioversions
🪝 What's the latest version for each database?
https://github.com/biopragmatics/bioversions
biopragmatics
Last synced: about 12 hours ago
JSON representation
🪝 What's the latest version for each database?
- Host: GitHub
- URL: https://github.com/biopragmatics/bioversions
- Owner: biopragmatics
- License: mit
- Created: 2020-12-05T17:48:54.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2024-10-30T01:02:36.000Z (2 months ago)
- Last Synced: 2024-10-30T03:51:15.722Z (2 months ago)
- Topics: biopragmatics
- Language: Python
- Homepage: https://biopragmatics.github.io/bioversions
- Size: 4.46 MB
- Stars: 26
- Watchers: 3
- Forks: 7
- Open Issues: 12
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
Bioversions
What's the current version for each biological database?
A daily updated static listing of all current versions (that are incorporated) can be found at
https://biopragmatics.github.io/bioversions.
## 💪 Getting Started
```python
import bioversions
assert bioversions.get_version('biogrid') == '4.2.192', 'This was true on Dec 5th, 2020!'
# If you want more information, use the resolve() function
bioversion = bioversions.resolve('biogrid')
assert bioversion.version == '4.2.192'
```
By default, the results are cached and only refreshed once per day with the help
of [`cachier`](https://github.com/shaypal5/cachier). The cache is stored in `~/.data/bioversions`. The cache location
can be overridden by setting the
`BIOVERSIONS_HOME` environment variable via [`pystow`](https://github.com/cthoyt/pystow).
## 🌐 Web Application
While https://biopragmatics.github.io/bioversions provides a daily updated static listing of the database, you can run a
dynamic version with an API from your shell with:
```bash
$ bioversions web
```
Options can be listed with `bioversions web --help`.
You can navigate to http://localhost:5000 to see all versions as HTML or programmatically resolve given databases with
the
`http://localhost:5000/database/` endpoint like in the following:
```python
import requests
res = requests.get('http://localhost:5000/database/biogrid').json()
assert res['success']
assert res['result']['name'] == 'BioGRID'
assert res['result']['version'] == '4.2.192', 'This was true on Dec 5th, 2020!'
```
## CLI Usage
You can use `bioversions get` to incorporate the latest versions in your shell scripts or REPL usage like in:
```bash
$ wget "https://downloads.thebiogrid.org/Download/BioGRID/Release-Archive/BIOGRID-$(bioversions get biogrid)/BIOGRID-ALL-$(bioversions get biogrid).mitab.zip"
```
## 🚀 Installation
The most recent release can be installed from
[PyPI](https://pypi.org/project/bioversions/) with:
```console
python3 -m pip install bioversions
```
The most recent code and data can be installed directly from GitHub with:
```console
python3 -m pip install git+https://github.com/biopragmatics/bioversions.git
```
## 👐 Contributing
Contributions, whether filing an issue, making a pull request, or forking, are appreciated. See
[CONTRIBUTING.md](https://github.com/biopragmatics/bioversions/blob/master/.github/CONTRIBUTING.md)
for more information on getting involved.
To add more databases to the list, you can create a new submodule of
`bioversions.sources` and extend the `bioversions.utils.Getter` class to identify the most recent version for your
target database. See
`bioversions.sources.biogrid` as an example.
## 👋 Attribution
### ⚖️ License
The code in this package is licensed under the MIT License.
### 🎁 Support
The Bioversions service was originally developed by the [INDRA Lab](https://indralab.github.io), a part of the
[Laboratory of Systems Pharmacology](https://hits.harvard.edu/the-program/laboratory-of-systems-pharmacology/about/)
and the [Harvard Program in Therapeutic Science (HiTS)](https://hits.harvard.edu)
at [Harvard Medical School](https://hms.harvard.edu/).
### 💰 Funding
The development of this package was partially funded by the DARPA Young Faculty Award W911NF2010255 (PI:
Benjamin M. Gyori).
### 🍪 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
See developer instructions
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/bioversions.git
cd bioversions
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/bioversions/actions?query=workflow%3ATests).
### 📖 Building the Documentation
The documentation can be built locally using the following:
```console
git clone git+https://github.com/biopragmatics/bioversions.git
cd bioversions
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`](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`](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`](.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/bioversions
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/bioversions/version.py`,
and [`docs/source/conf.py`](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/bioversions/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.