https://github.com/hypothesis/h-vialib
Library functions for use with Via
https://github.com/hypothesis/h-vialib
Last synced: 11 months ago
JSON representation
Library functions for use with Via
- Host: GitHub
- URL: https://github.com/hypothesis/h-vialib
- Owner: hypothesis
- License: bsd-2-clause
- Created: 2020-08-28T11:30:06.000Z (almost 6 years ago)
- Default Branch: main
- Last Pushed: 2025-06-13T14:48:57.000Z (about 1 year ago)
- Last Synced: 2025-07-01T16:55:40.462Z (12 months ago)
- Language: Python
- Size: 124 KB
- Stars: 2
- Watchers: 5
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# h-vialib
Library functions for use with Via.
Usage
-----
This is an internal library, mostly of interest to maintainers of
[Via](https://github.com/hypothesis/via) and related components.
Some items of interest:
* [Configuration](https://github.com/hypothesis/h-vialib/blob/main/src/h_vialib/configuration.py) - Configuration parameter management
## Setting up Your h-vialib Development Environment
First you'll need to install:
* [Git](https://git-scm.com/).
On Ubuntu: `sudo apt install git`, on macOS: `brew install git`.
* [GNU Make](https://www.gnu.org/software/make/).
This is probably already installed, run `make --version` to check.
* [pyenv](https://github.com/pyenv/pyenv).
Follow the instructions in pyenv's README to install it.
The **Homebrew** method works best on macOS.
The **Basic GitHub Checkout** method works best on Ubuntu.
You _don't_ need to set up pyenv's shell integration ("shims"), you can
[use pyenv without shims](https://github.com/pyenv/pyenv#using-pyenv-without-shims).
Then to set up your development environment:
```terminal
git clone https://github.com/hypothesis/h-vialib.git
cd h-vialib
make help
```
## Releasing a New Version of the Project
1. First, to get PyPI publishing working you need to go to:
and add h-vialib to the `PYPI_TOKEN` secret's selected
repositories.
2. Now that the h-vialib project has access to the `PYPI_TOKEN` secret
you can release a new version by just [creating a new GitHub release](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository).
Publishing a new GitHub release will automatically trigger
[a GitHub Actions workflow](.github/workflows/pypi.yml)
that will build the new version of your Python package and upload it to
.
## Changing the Project's Python Versions
To change what versions of Python the project uses:
1. Change the Python versions in the
[cookiecutter.json](.cookiecutter/cookiecutter.json) file. For example:
```json
"python_versions": "3.10.4, 3.9.12",
```
2. Re-run the cookiecutter template:
```terminal
make template
```
3. Commit everything to git and send a pull request
## Changing the Project's Python Dependencies
To change the production dependencies in the `setup.cfg` file:
1. Change the dependencies in the [`.cookiecutter/includes/setuptools/install_requires`](.cookiecutter/includes/setuptools/install_requires) file.
If this file doesn't exist yet create it and add some dependencies to it.
For example:
```
pyramid
sqlalchemy
celery
```
2. Re-run the cookiecutter template:
```terminal
make template
```
3. Commit everything to git and send a pull request
To change the project's formatting, linting and test dependencies:
1. Change the dependencies in the [`.cookiecutter/includes/tox/deps`](.cookiecutter/includes/tox/deps) file.
If this file doesn't exist yet create it and add some dependencies to it.
Use tox's [factor-conditional settings](https://tox.wiki/en/latest/config.html#factors-and-factor-conditional-settings)
to limit which environment(s) each dependency is used in.
For example:
```
lint: flake8,
format: autopep8,
lint,tests: pytest-faker,
```
2. Re-run the cookiecutter template:
```terminal
make template
```
3. Commit everything to git and send a pull request