MyVenv
MyVenv is a simple Windows utility that helps you create or activate a Python virtual environment directly in the current CMD shell. With MyVenv, you can streamline your virtual environment management workflow using a single command.
Features
- Automatically creates a virtual environment if it doesn't exist.
- Activates the virtual environment in the current CMD shell.
- Adds the virtual environment folder to
.gitignoreto prevent accidental commits.
Installation
You can install MyVenv via pip:
pip install myvenv
Usage
After installing MyVenv, you can use the myvenv.bat script in your terminal to create or activate a virtual environment.
Command Syntax
myvenv [ENV_NAME]
ENV_NAME(optional): The name of the virtual environment folder. Defaults tovenvif not provided.
Examples
Create and Activate Default Virtual Environment
myvenv
This creates (if it doesn't already exist) and activates a virtual environment named venv.
Create and Activate a Custom Virtual Environment
myvenv mycustomenv
This creates (if it doesn't already exist) and activates a virtual environment named mycustomenv.
How It Works
- Environment Name: The script checks for the provided environment name or defaults to
venv. - Virtual Environment Creation: If the specified folder doesn't exist, it creates a virtual environment using
python -m venv. - Git Ignore Update: The script ensures the virtual environment folder is listed in
.gitignoreto prevent accidental commits. - Activation: The script activates the virtual environment in the current CMD shell.
Project Structure
myvenv.bat: Batch script for managing virtual environments.setup.py: Python setup script for packaging and distribution.
License
This project is licensed under the MIT License. See the LICENSE file for details.
Contributing
Contributions are welcome! If you have suggestions or improvements, feel free to submit a pull request or open an issue.
Author
ILikeAI (Josh)
GitHub Profile
Feedback
If you encounter any issues or have ideas for improvement, please let us know by creating an issue in the GitHub repository.
Metadata
Release files for myvenv 0.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 | Actions |
|---|---|---|---|---|
| myvenv-0.1.0.tar.gz | 2.9 kB | Without provenance | Details for myvenv-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| myvenv-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for myvenv-0.1.0-py3-none-any.whl |
Total release size: 5.9 kB
Release files / myvenv-0.1.0.tar.gz
| Download URL | myvenv-0.1.0.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62c54245cecf0e19161a1c7e0ad6775a25cda7e993c787d20b2021ea3e7770a1
|
|
BLAKE2b-256 checksum How to use checksums |
24f143e97eb2842bb0284e3628260f7a2e88a7dcb7bfeba55902db83485fb5b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.3
|
Release files / myvenv-0.1.0-py3-none-any.whl
| Download URL | myvenv-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
29d9584061d92f0542505022ea152d6d3a4660f5a5e28437d8fb2680c0652fae
|
|
BLAKE2b-256 checksum How to use checksums |
2417f1e3914958fa8ab79bf127c5998fb5cf1a5d7e25d8df7d8c8e3c624c537e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.3
|
Security for myvenv 0.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.