This project has been archived by its maintainers, and is no longer receiving any updates.
tox-venv
What is tox-venv?
tox-venv is a plugin that uses Python 3’s builtin venv module for creating test environments, instead of creating them with the virtualenv package. For Python versions that do not include venv (namely 3.2 and earlier), this package does nothing and reverts to tox’s default implementation.
Why use tox-venv?
virtualenv is historically Python 2/3 compatible, however to achieve this, it ships some files that are pinned at their Python 2.6 version, such as the site module (see: pypa/virtualenv#355). This has a few effects:
Builds using the -Werror option fail, as the deprecations are raised before the test suite can run.
Users cannot take advantage of newer features of the site module in their test environments.
Eventually, these deprecations will become exceptions in future versions of Python.
By using the builtin venv module, these issues can be avoided.
Installation & Usage
To use tox-venv, install it alongside tox in your environment. Then, run tox as normal - no configuration necessary.
$ pip install tox tox-venv
$ tox
If you have already ran tox, it’s necessary to recreate the test envs. Either run tox --recreate, or delete the .tox directory.
Compatibility
tox-venv is compatible with both Python 2 and 3, however it only creates test environments in Python 3.3 and later. Python 3.3 environments are only partially compatible, as not all options (such as --copies/--symlinks) were supported. Environments for Python 3.4 and later are fully compatible.
Release process
Update changelog
Update package version in setup.py
Create git tag for version
Upload release to PyPI
$ pip install -U twine setuptools wheel
$ rm -rf dist/ build/
# python setup.py sdist bdist_wheel
$ twine upload dist/*
Metadata
Release files for tox-venv 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tox-venv-0.4.0.tar.gz | 15.9 kB | Without provenance | Details for tox-venv-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tox_venv-0.4.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for tox_venv-0.4.0-py2.py3-none-any.whl |
Total release size: 21.3 kB
Release files / tox-venv-0.4.0.tar.gz
| Download URL | tox-venv-0.4.0.tar.gz |
|---|---|
| Size | 15.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea29dc7b21a03951e1e2bd7f3474bbf315657c5454224a5674b2896e9bbb795c
|
|
BLAKE2b-256 checksum How to use checksums |
f16a5eb11089894bba3876ff51bf4a93e3fed4ef7d51ae9d0a2a8de5f7e13674
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.1
|
Release files / tox_venv-0.4.0-py2.py3-none-any.whl
| Download URL | tox_venv-0.4.0-py2.py3-none-any.whl |
|---|---|
| Size | 5.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
22c2aba71a991d4adf6902253fa07b3a241d28e4e901cbc9dc86ee8eeaa8d4b4
|
|
BLAKE2b-256 checksum How to use checksums |
11923bf5efd94dcc470b15d351ba77294bb3d7faf221b1c9912c08dff7ce33a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.1
|
Security for tox-venv 0.4.0
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.