vvenv 0.1.0__tar.gz

vvenv-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 venvy contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

vvenv-0.1.0/PKG-INFO

@@ -0,0 +1,270 @@
+Metadata-Version: 2.4
+Name: vvenv
+Version: 0.1.0
+Summary: Smart Python virtual environment manager — like package.json but for Python
+Author: venvy contributors
+License: MIT
+Project-URL: Homepage, https://github.com/yourorg/venvy
+Project-URL: Repository, https://github.com/yourorg/venvy
+Project-URL: Issues, https://github.com/yourorg/venvy/issues
+Keywords: venv,virtualenv,pip,requirements,cli,dev-tools
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: System :: Installation/Setup
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: typer>=0.9.0
+Requires-Dist: rich>=13.0.0
+Requires-Dist: watchdog>=3.0.0
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0; extra == "dev"
+Requires-Dist: pytest-cov>=4.0; extra == "dev"
+Requires-Dist: black>=23.0; extra == "dev"
+Requires-Dist: ruff>=0.1.0; extra == "dev"
+Requires-Dist: mypy>=1.0; extra == "dev"
+Dynamic: license-file
+
+# venvy 🐍
+
+> **Smart Python virtual environment manager — like `package.json` for Python.**
+
+venvy takes the pain out of managing Python virtual environments and `requirements.txt`. It works cross-platform (Windows + macOS/Linux) and integrates seamlessly into your shell so that `pip install` automatically tracks packages.
+
+---
+
+## Features
+
+| Feature | Description |
+|---------|-------------|
+| `venvy create venv` | Interactively create & configure a venv |
+| `venvy pip install <pkg>` | Install + auto-add to requirements |
+| `venvy pip uninstall <pkg>` | Uninstall + auto-remove from requirements |
+| `venvy status` | Show venv & requirements info |
+| `venvy sync` | Install all packages from requirements |
+| `venvy list` | List tracked packages |
+| Shell integration | `venvy +` / `venvy -` for activate/deactivate |
+| Existing venv support | Works with any venv, not just venvy-created ones |
+
+---
+
+## Installation
+
+```bash
+# Recommended: install globally with pipx
+pipx install venvy
+
+# Or with pip (global)
+pip install venvy
+
+# Or with pip --user
+pip install --user venvy
+```
+
+---
+
+## Quick Start
+
+### 1. Initialize a project
+
+```bash
+cd my-project
+venvy create venv
+```
+
+You'll be asked:
+
+```
+venvy — virtual environment setup
+────────────────────────────────────────
+  [1/2] Install ipykernel (for Jupyter notebook support)? [y/N]: n
+  [2/2] Requirements file name [requirements.txt]: 
+```
+
+venvy then:
+- Creates `.venv/`
+- Upgrades pip
+- Installs ipykernel (if chosen)
+- Installs existing requirements (if any)
+- Saves config to `.venvy/config.json`
+
+### 2. Activate / deactivate
+
+**Without shell integration (always works):**
+```bash
+# macOS / Linux
+source .venv/bin/activate
+
+# Windows (cmd)
+.venv\Scripts\activate.bat
+
+# Windows (PowerShell)
+.venv\Scripts\Activate.ps1
+```
+
+**With shell integration (recommended):**
+```bash
+# Set up once:
+echo 'eval "$(venvy shell-init)"' >> ~/.bashrc  # or ~/.zshrc
+source ~/.bashrc
+
+# Then use anywhere:
+venvy +    # activate
+venvy -    # deactivate
+```
+
+### 3. Install packages (auto-tracked)
+
+```bash
+# With venvy (always works):
+venvy pip install requests httpx
+
+# With shell integration, plain pip works too:
+pip install requests httpx
+# → automatically added to requirements.txt!
+
+pip uninstall requests
+# → automatically removed from requirements.txt!
+```
+
+### 4. Clone a project and restore dependencies
+
+```bash
+git clone https://github.com/user/project
+cd project
+venvy create venv   # installs from existing requirements.txt
+# or:
+venvy sync          # if venv already exists
+```
+
+---
+
+## Shell Integration (Recommended)
+
+Add to your `~/.bashrc` or `~/.zshrc`:
+
+```bash
+eval "$(venvy shell-init)"
+```
+
+Restart your terminal. Now:
+
+```bash
+venvy +              # activates the venv (like npm run)
+venvy -              # deactivates the venv
+
+pip install <pkg>    # auto-updates requirements.txt ✓
+pip uninstall <pkg>  # auto-removes from requirements.txt ✓
+```
+
+### Windows (PowerShell)
+
+Add to your `$PROFILE`:
+
+```powershell
+venvy shell-init | Invoke-Expression
+```
+
+---
+
+## Commands Reference
+
+```
+venvy create venv [options]     Create virtual environment
+  --name  -n    Venv directory name (default: .venv)
+  --requirements -r  Requirements file name
+  --ipykernel   Pre-select ipykernel
+  --yes -y      Skip prompts, use defaults
+
+venvy pip install <packages>    Install & track packages
+  --upgrade -U  Upgrade packages
+
+venvy pip uninstall <packages>  Uninstall & untrack packages
+  --yes -y      Skip confirmation
+
+venvy status                    Show environment info
+venvy list                      List tracked packages
+venvy sync                      Install all requirements
+
+venvy shell-init                Print shell integration script
+venvy +                         Activation hint / activate (shell integration)
+venvy -                         Deactivation hint / deactivate (shell integration)
+
+venvy --version                 Show version
+```
+
+---
+
+## Project Structure
+
+After `venvy create venv`:
+
+```
+my-project/
+├── .venv/                  ← virtual environment
+├── .venvy/
+│   └── config.json         ← venvy project config
+├── requirements.txt        ← auto-managed!
+└── your code...
+```
+
+### `.venvy/config.json` example
+
+```json
+{
+  "venv_name": ".venv",
+  "requirements_file": "requirements.txt",
+  "install_ipykernel": false
+}
+```
+
+Add `.venvy/` to your `.gitignore` or commit it — your choice. Commit `requirements.txt` always.
+
+---
+
+## Using an Existing Venv
+
+venvy works with any existing virtual environment — it doesn't need to have created it. As long as:
+
+1. The venv is active (`$VIRTUAL_ENV` is set), **or**
+2. A `.venv`, `venv`, `env`, or `.env` directory exists in the project
+
+venvy will find it and manage `requirements.txt` accordingly.
+
+---
+
+## Philosophy
+
+venvy brings `package.json`-style dependency management to Python:
+
+| npm / Node | venvy / Python |
+|------------|----------------|
+| `npm init` | `venvy create venv` |
+| `npm install <pkg>` | `venvy pip install <pkg>` |
+| `npm uninstall <pkg>` | `venvy pip uninstall <pkg>` |
+| `npm install` (restore) | `venvy sync` |
+| `package.json` | `requirements.txt` |
+| `node_modules/` | `.venv/` |
+
+---
+
+## Development
+
+```bash
+git clone https://github.com/yourorg/venvy
+cd venvy
+python -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev]"
+pytest
+```
+
+---
+
+## License
+
+MIT

vvenv-0.1.0/README.md

@@ -0,0 +1,239 @@
+# venvy 🐍
+
+> **Smart Python virtual environment manager — like `package.json` for Python.**
+
+venvy takes the pain out of managing Python virtual environments and `requirements.txt`. It works cross-platform (Windows + macOS/Linux) and integrates seamlessly into your shell so that `pip install` automatically tracks packages.
+
+---
+
+## Features
+
+| Feature | Description |
+|---------|-------------|
+| `venvy create venv` | Interactively create & configure a venv |
+| `venvy pip install <pkg>` | Install + auto-add to requirements |
+| `venvy pip uninstall <pkg>` | Uninstall + auto-remove from requirements |
+| `venvy status` | Show venv & requirements info |
+| `venvy sync` | Install all packages from requirements |
+| `venvy list` | List tracked packages |
+| Shell integration | `venvy +` / `venvy -` for activate/deactivate |
+| Existing venv support | Works with any venv, not just venvy-created ones |
+
+---
+
+## Installation
+
+```bash
+# Recommended: install globally with pipx
+pipx install venvy
+
+# Or with pip (global)
+pip install venvy
+
+# Or with pip --user
+pip install --user venvy
+```
+
+---
+
+## Quick Start
+
+### 1. Initialize a project
+
+```bash
+cd my-project
+venvy create venv
+```
+
+You'll be asked:
+
+```
+venvy — virtual environment setup
+────────────────────────────────────────
+  [1/2] Install ipykernel (for Jupyter notebook support)? [y/N]: n
+  [2/2] Requirements file name [requirements.txt]: 
+```
+
+venvy then:
+- Creates `.venv/`
+- Upgrades pip
+- Installs ipykernel (if chosen)
+- Installs existing requirements (if any)
+- Saves config to `.venvy/config.json`
+
+### 2. Activate / deactivate
+
+**Without shell integration (always works):**
+```bash
+# macOS / Linux
+source .venv/bin/activate
+
+# Windows (cmd)
+.venv\Scripts\activate.bat
+
+# Windows (PowerShell)
+.venv\Scripts\Activate.ps1
+```
+
+**With shell integration (recommended):**
+```bash
+# Set up once:
+echo 'eval "$(venvy shell-init)"' >> ~/.bashrc  # or ~/.zshrc
+source ~/.bashrc
+
+# Then use anywhere:
+venvy +    # activate
+venvy -    # deactivate
+```
+
+### 3. Install packages (auto-tracked)
+
+```bash
+# With venvy (always works):
+venvy pip install requests httpx
+
+# With shell integration, plain pip works too:
+pip install requests httpx
+# → automatically added to requirements.txt!
+
+pip uninstall requests
+# → automatically removed from requirements.txt!
+```
+
+### 4. Clone a project and restore dependencies
+
+```bash
+git clone https://github.com/user/project
+cd project
+venvy create venv   # installs from existing requirements.txt
+# or:
+venvy sync          # if venv already exists
+```
+
+---
+
+## Shell Integration (Recommended)
+
+Add to your `~/.bashrc` or `~/.zshrc`:
+
+```bash
+eval "$(venvy shell-init)"
+```
+
+Restart your terminal. Now:
+
+```bash
+venvy +              # activates the venv (like npm run)
+venvy -              # deactivates the venv
+
+pip install <pkg>    # auto-updates requirements.txt ✓
+pip uninstall <pkg>  # auto-removes from requirements.txt ✓
+```
+
+### Windows (PowerShell)
+
+Add to your `$PROFILE`:
+
+```powershell
+venvy shell-init | Invoke-Expression
+```
+
+---
+
+## Commands Reference
+
+```
+venvy create venv [options]     Create virtual environment
+  --name  -n    Venv directory name (default: .venv)
+  --requirements -r  Requirements file name
+  --ipykernel   Pre-select ipykernel
+  --yes -y      Skip prompts, use defaults
+
+venvy pip install <packages>    Install & track packages
+  --upgrade -U  Upgrade packages
+
+venvy pip uninstall <packages>  Uninstall & untrack packages
+  --yes -y      Skip confirmation
+
+venvy status                    Show environment info
+venvy list                      List tracked packages
+venvy sync                      Install all requirements
+
+venvy shell-init                Print shell integration script
+venvy +                         Activation hint / activate (shell integration)
+venvy -                         Deactivation hint / deactivate (shell integration)
+
+venvy --version                 Show version
+```
+
+---
+
+## Project Structure
+
+After `venvy create venv`:
+
+```
+my-project/
+├── .venv/                  ← virtual environment
+├── .venvy/
+│   └── config.json         ← venvy project config
+├── requirements.txt        ← auto-managed!
+└── your code...
+```
+
+### `.venvy/config.json` example
+
+```json
+{
+  "venv_name": ".venv",
+  "requirements_file": "requirements.txt",
+  "install_ipykernel": false
+}
+```
+
+Add `.venvy/` to your `.gitignore` or commit it — your choice. Commit `requirements.txt` always.
+
+---
+
+## Using an Existing Venv
+
+venvy works with any existing virtual environment — it doesn't need to have created it. As long as:
+
+1. The venv is active (`$VIRTUAL_ENV` is set), **or**
+2. A `.venv`, `venv`, `env`, or `.env` directory exists in the project
+
+venvy will find it and manage `requirements.txt` accordingly.
+
+---
+
+## Philosophy
+
+venvy brings `package.json`-style dependency management to Python:
+
+| npm / Node | venvy / Python |
+|------------|----------------|
+| `npm init` | `venvy create venv` |
+| `npm install <pkg>` | `venvy pip install <pkg>` |
+| `npm uninstall <pkg>` | `venvy pip uninstall <pkg>` |
+| `npm install` (restore) | `venvy sync` |
+| `package.json` | `requirements.txt` |
+| `node_modules/` | `.venv/` |
+
+---
+
+## Development
+
+```bash
+git clone https://github.com/yourorg/venvy
+cd venvy
+python -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev]"
+pytest
+```
+
+---
+
+## License
+
+MIT

vvenv-0.1.0/pyproject.toml

@@ -0,0 +1,67 @@
+[build-system]
+requires = ["setuptools", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "vvenv"
+version = "0.1.0"
+description = "Smart Python virtual environment manager — like package.json but for Python"
+readme = "README.md"
+license = { text = "MIT" }
+authors = [{ name = "venvy contributors" }]
+requires-python = ">=3.8"
+keywords = ["venv", "virtualenv", "pip", "requirements", "cli", "dev-tools"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+    "Topic :: System :: Installation/Setup",
+]
+dependencies = [
+    "typer>=0.9.0",
+    "rich>=13.0.0",
+    "watchdog>=3.0.0",
+]
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=7.0",
+    "pytest-cov>=4.0",
+    "black>=23.0",
+    "ruff>=0.1.0",
+    "mypy>=1.0",
+]
+
+[project.scripts]
+venvy = "venvy.cli:app"
+
+[project.urls]
+Homepage = "https://github.com/yourorg/venvy"
+Repository = "https://github.com/yourorg/venvy"
+Issues = "https://github.com/yourorg/venvy/issues"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+venvy = ["py.typed"]
+
+[tool.black]
+line-length = 88
+target-version = ["py38", "py39", "py310", "py311", "py312"]
+
+[tool.ruff]
+line-length = 88
+select = ["E", "W", "F", "I", "UP", "B", "SIM"]
+ignore = ["E501"]
+target-version = "py38"
+
+[tool.mypy]
+python_version = "3.8"
+strict = true
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

vvenv-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

vvenv-0.1.0/src/venvy/__init__.py

@@ -0,0 +1,9 @@
+"""
+venvy — Smart Python virtual environment manager.
+
+Like package.json for Python projects.
+"""
+
+__version__ = "0.1.0"
+__author__ = "venvy contributors"
+__all__ = ["__version__"]