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
Metadata
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 | |
|---|---|---|---|
| py2venv-1.1.tar.gz | 2.5 kB | Details |
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 |