Skip to main content

uvoxen - generate test configuration files and run tests

[Home | sourcehut | PyPI | ReadTheDocs]

Overview

The uvoxen tool allows test environments to be defined in the pyproject.toml file with a syntax relatively similar to the one used for Tox configuration. It can then:

  • run tests defined in these environments using the uv tool
  • output Tox configuration and run Tox instead
  • export the dependency groups into text files

See the Getting started section for an introduction.

The uvoxen tool expects test dependencies to be defined as PEP 735 dependency groups in the pyproject.toml file.

Examples

These are some of the ways to use uvoxen; see the Getting started and the Configuration sections for more information.

Run tests using uv

The uvoxen uv run command runs one or more test environments in succession, recreating the .venv virtual environment in between. The commands defined in the environments are run using the uv tool.

uvoxen uv run

If the --python (-p) command-line option is specified before the uv subcommand, uvoxen will use that Python version to run the tests:

uvoxen -p 3.10 uv run -e mypy,unit-tests

If the special value supported is passed as a Python version, uvoxen will run all the selected environments for all the Python versions that are listed as supported in the project.classifiers section of the pyproject.toml file:

uvoxen -p supported uv run

Generate a Tox configuration file

The uvoxen tox generate command will export the environment definitions into a tox.ini file so that Tox may be used later (or separately):

uvoxen tox generate

If the --check command-line option is specified, uvoxen will not modify the tox.ini file, but it will exit with a non-zero code if any changes need to be made:

uvoxen tox generate --check

Generate requirements files from the dependency groups

The uvoxen req generate command will export the list of dependencies defined in the specified dependency group into a text file suitable for use with e.g. the ReadTheDocs mkdocs runner:

uvoxen req generate -g docs

If the --output (-o) option is not specified, the generated file will be named requirements/<group>.txt, e.g. requirements/docs.txt.

If the --check command-line option is specified, uvoxen will not modify the requirements/docs.txt file, but it will exit with a non-zero code if any changes need to be made:

uvoxen req generate --check -g docs

Contact

The uvoxen tool was written by Peter Pentchev. It is developed in a sourcehut repository. This documentation is hosted at Ringlet with a copy at ReadTheDocs.

Metadata

Release files for uvoxen 0.2.8

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

Source distribution (sdist)

Source distribution for uvoxen 0.2.8
File Size Uploaded Provenance Actions
uvoxen-0.2.8.tar.gz 111.7 kB Without provenance Details for uvoxen-0.2.8.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for uvoxen 0.2.8
File Interpreter ABI Platform Actions
uvoxen-0.2.8-py3-none-any.whl Python 3 none any Details for uvoxen-0.2.8-py3-none-any.whl

Total release size: 133.2 kB

Release files / uvoxen-0.2.8.tar.gz

Download URL uvoxen-0.2.8.tar.gz
Size 111.7 kB
Tags Source
SHA-256 checksum
How to use checksums
42d988a458719f055b771b694badc006d2c081f43adbb4243502b72aa4cc050b
BLAKE2b-256 checksum
How to use checksums
eeed4748ddc89a39044abe19fca02e5b31378ea6cfb317420b82a0cf0d9de4f2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.10

Release files / uvoxen-0.2.8-py3-none-any.whl

Download URL uvoxen-0.2.8-py3-none-any.whl
Size 21.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a0738636af5b35b2ace0d6f64b945ba6805c145f0034f64498509b8641338911
BLAKE2b-256 checksum
How to use checksums
86034010d2b811f11c0eada13b9442456a0b5ef0e74270baebaa1e44958e295c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.10

Security for uvoxen 0.2.8

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page