py2venv
Provides a simple “shortcut” from virtualenv to venv on python 2.
Pretty much everything I do is in python3, where I use venv for every single project I work on.
Occasionally I need my CI to also test / build / deploy to python2 as well. As is stands, I generally end up with annoyingly complex startups scripts in ci that has to check which version is being being run and then either use python -m venv .venv on 3 or python -m pip install virtualenv; python -m virtualenv .venv for 2.
It would be much better if I could just use python -m venv .venv everywhere, but venv has not been backported. This package is a pretty decent workaround.
py2venv can be pre-installed on any python. On python3 it does nothing. On python 2 it ensures virtualenv has been installed and provides a ‘venv’ module entrypoint:
python -m pip install py2venv python -m venv .venv
1 maintainer
Metadata
1 maintainer
Release files for py2venv 1.1
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 |
|---|---|---|---|---|
| py2venv-1.1.tar.gz | 2.5 kB | Without provenance | Details for py2venv-1.1.tar.gz |
Release files / py2venv-1.1.tar.gz
| Download URL | py2venv-1.1.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8b3245362c362ffe81d66a2ce13be82da4c51e84ed5cbc19844ec84600c1dc89
|
|
BLAKE2b-256 checksum How to use checksums |
bccd97339b0b0932c2a9cddc972b71375e4e66d769fb5f39eefa556c57952846
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for py2venv 1.1
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.
