runvenv
Runs a script or module in a venv and forwards any parameter.
This includes non positional arguments like --help, --init, --path, --check, --requirements, etc.
With no parameters given this help will be shown. To only create a venv and not run anything
you can use the --init parameter. If the venv does not exist yet, it will create it and also install
all requirements in either reqirements.txt, .requirements.txt or .requirements.venv if available.
To check if a venv is already set up use the parameter --check. Depending on the status exit code is:
- 0 = up-to-date
- 1 = available but not up-to-date
- 2 = not available
A custom venv path or requirements file can be configured via parameters.
1 maintainer
Metadata
1 maintainer
Release files for runvenv 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| runvenv-0.5.1-py3-none-any.whl | Python 3 | none | any | Details for runvenv-0.5.1-py3-none-any.whl |
Release files / runvenv-0.5.1-py3-none-any.whl
| Download URL | runvenv-0.5.1-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a48e30f2a1132435d1ab9de6613fbdc91f296061c233912547a4168a68917ac
|
|
BLAKE2b-256 checksum How to use checksums |
03a0cd9f8d1a71b2437ebb95491fe7b3a9bd53945cdce6e546e14de4d4106613
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.0 CPython/3.13.7
|
Security for runvenv 0.5.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.
