PyEM: Project-level virtual environment management
PyEM manages multiple virtual environments local to projects. It provides shortcuts to create, remove, switch between, and run commands against virtual environments created against various Python interpreters.
Install
I recommend using pipx:
pipx install pyem # If you need to support Python without the builtin venv module. pipx inject pyem virtualenv
In Action
Add a virtual environment besides the file pyproject.toml:
# Based on a command. pyem venv add python3.7 # Based on interpreter found by the Python launcher. pyem venv add 3.6 # Based on an executable. pyem venv add /usr/local/bin/pypy3
The second variant relies on the Python launcher to locate an interpreter. This tool should be installed by default if you use the officlal installer on Windows (and do not explicitly choose not to install it). For other platforms, Python launcher for UNIX by Brett Cannon can be used as an alternative.
List managed virtual environments:
$ pyem venv list Quintuplet ============================================= cpython-3.6-darwin-x86_64-f14a3513 cpython-3.7-darwin-x86_64-dbe83ac5 * pypy-3.6-darwin-x86_64-dc1298a1
Set active virtual environment:
$ pyem venv set 3.7 Switched to cpython-3.7-darwin-x86_64-dbe83ac5 $ pyem venv set 3.6 Error: name '3.6' is ambiguous; choose from: cpython-3.6-darwin-x86_64-f14a3513 pypy-3.6-darwin-x86_64-dc1298a1 $ pyem venv set cpython-3.6 Switched to cpython-3.6-darwin-x86_64-f14a3513
Run a command inside a virtual environment:
$ pyem poetry run python -c "import sys; print(sys.executable)" /tmp/exampleproject/.venvs/bin/python $ pyem --spec=pypy-3.6 pipenv run pypy3 -c "import sys; print(sys.executable)" /tmp/exampleproject/.venvs/bin/pypy3
How does this work?
PyEM sets environment variables VIRTUAL_ENV and PATH, and hand off control to subprocess for the command specified. This is enough to trick a lot of Python project tools, including the Python launcher, Poetry, and Pipenv. Python interpreters with venv support (e.g. CPython 3.3 or later) should also integrate seamlessly.
Tips and Tricks
Flit on Windows
Flit has problems detecting the active virtual environment on Windows when installed into Python 3.7.2 or later. Use the following workaround (requires the Python launcher):
$ pyem flit install --python=py
Starting from Flit 2.1, you can also set the environment variable FLIT_INSTALL_PYTHON=py for the same effect. This is a good default even when you’re not using PyEM IMO; it makes more sense than installing into Flit’s environment.
This has been fixed in master (takluyver/flit#300), so Flit after 2.1.0 does not need this workaround.
Project without pyproject.toml
If your project does not use pyproject.toml, you can specify the project root explicitly:
pyem --project=./myproject add 3.8
The --project option is only required when creating a virtual environment. Subsequent commands should pick up the .venvs directory automatically, and use its location as the project root, even without the presence of pyproject.toml.
Call a virtual environment outside the project root
The --project option is also handy if you want to access a virtual environment when you’re outside of the project root. This command lists installed packages in the 3.7 virtual environment of another-project:
pyem --project=../another-project --python=3.7 pip list
1 maintainer
Metadata
1 maintainer
Release files for pyem 2.1.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 | |
|---|---|---|---|---|
| pyem-2.1.0.tar.gz | 14.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyem-2.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.2 kB
Release files / pyem-2.1.0.tar.gz
| Download URL | pyem-2.1.0.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5234a20427ab2813a8a0bf1e9112d4d854b1b0502b3e63d17c1b1a3c4be9340e
|
|
BLAKE2b-256 checksum How to use checksums |
1eb64cb6568b9fbfcc972a68c48f8b9dad2d6309fef298777523776c9a33bcd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.22.0
|
Release files / pyem-2.1.0-py3-none-any.whl
| Download URL | pyem-2.1.0-py3-none-any.whl |
|---|---|
| Size | 17.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1970b55569d21e80734c428d6c3726aa6f2620c8c547c95bb0a5f3faef8e3eb2
|
|
BLAKE2b-256 checksum How to use checksums |
c1e098abd4c2db9f684554306b45ef0855913e4e51f36fac74c63f393cc82080
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.22.0
|
Security for pyem 2.1.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.
