h-vialib

Library functions for use with Via.

Usage

This is an internal library, mostly of interest to maintainers of Via and related components.

Some items of interest:

Configuration - Configuration parameter management

Setting up Your h-vialib Development Environment

First you'll need to install:

Git. On Ubuntu: sudo apt install git, on macOS: brew install git.
GNU Make. This is probably already installed, run make --version to check.
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.

Then to set up your development environment:

git clone https://github.com/hypothesis/h-vialib.git
cd h-vialib
make help

Releasing a New Version of the Project

First, to get PyPI publishing working you need to go to: https://github.com/organizations/hypothesis/settings/secrets/actions/PYPI_TOKEN and add h-vialib to the PYPI_TOKEN secret's selected repositories.
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. Publishing a new GitHub release will automatically trigger a GitHub Actions workflow that will build the new version of your Python package and upload it to https://pypi.org/project/h-vialib.

Changing the Project's Python Versions

To change what versions of Python the project uses:

Change the Python versions in the cookiecutter.json file. For example:
```
"python_versions": "3.10.4, 3.9.12",
```
Re-run the cookiecutter template:
```
make template
```
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:

Change the dependencies in the .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
```
Re-run the cookiecutter template:
```
make template
```
Commit everything to git and send a pull request

To change the project's formatting, linting and test dependencies:

Change the dependencies in the .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 to limit which environment(s) each dependency is used in. For example:
```
lint: flake8,
format: autopep8,
lint,tests: pytest-faker,
```
Re-run the cookiecutter template:
```
make template
```
Commit everything to git and send a pull request

Metadata

Release files for h-vialib 1.3.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for h-vialib 1.3.2
File	Size	Uploaded	Provenance
h_vialib-1.3.2.tar.gz	28.7 kB	Jan 10, 2025	Without provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for h-vialib 1.3.2
File	Interpreter	ABI	Platform	Reset
h_vialib-1.3.2-py3-none-any.whl 14.9 kB Jan 10, 2025 Without provenance	Python 3	none	any	Details

Total release size: 43.6 kB

Release files / h_vialib-1.3.2.tar.gz

Download URL	h_vialib-1.3.2.tar.gz
Size	28.7 kB
Tags	Source
SHA-256 checksum How to use checksums	`3cb98a1c516fb6a1d2ab598a88fb7e857aec0fc8ec0ee2d193a0d2565863933f`
BLAKE2b-256 checksum How to use checksums	`5cd12b789759c7fe43f90e935c932d0d3222d3effa20293fd1ea01b2f99b2753`
Upload date	Jan 10, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/6.0.1 CPython/3.12.8`

Release files / h_vialib-1.3.2-py3-none-any.whl

Download URL	h_vialib-1.3.2-py3-none-any.whl
Size	14.9 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`803fb110dccae55fba5b109110b2da3fe770d713b8ce4d265ae66da2a32fa2ff`
BLAKE2b-256 checksum How to use checksums	`6e9391e5a6c89bb0fc88f28cabc47f450442a5d63b93bd91c09f105771f8fba2`
Upload date	Jan 10, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/6.0.1 CPython/3.12.8`

Security for h-vialib 1.3.2

Report project as malware

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.