uvrev 0.1__tar.gz

uvrev-0.1/.gitignore

@@ -0,0 +1,219 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+.uv-cache/
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer,
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# IDEA
+.idea/

uvrev-0.1/.gitlab-ci.yml

@@ -0,0 +1,80 @@
+stages:
+  - test
+  - publish
+
+# Template: https://docs.astral.sh/uv/guides/integration/gitlab/#using-the-uv-image
+# Key points:
+# - Use ghcr.io/astral-sh/uv:<UV_VERSION>-python<PYTHON_VERSION>-<BASE_LAYER>
+# - Set UV_LINK_MODE=copy for GitLab’s mount behavior
+variables:
+  UV_VERSION: "0.9.23"
+  BASE_LAYER: "trixie"
+  UV_LINK_MODE: "copy"
+  UV_CACHE_DIR: "${CI_PROJECT_DIR}/.uv-cache"
+
+default:
+  image: "ghcr.io/astral-sh/uv:${UV_VERSION}-python${PYTHON_VERSION}-${BASE_LAYER}"
+  cache:
+    - key:
+        files:
+          - uv.lock
+        prefix: "uv-${PYTHON_VERSION}"
+      paths:
+        - $UV_CACHE_DIR
+
+# -------------------------
+# Tests (matrix 3.12..3.14)
+# -------------------------
+test:
+  stage: test
+  parallel:
+    matrix:
+      - PYTHON_VERSION: ["3.12", "3.13", "3.14"]
+  script:
+    - uv run --locked pre-commit run --all-files
+
+  after_script:
+    # Recommended by Astral to keep cache size under control in CI
+    - uv cache prune --ci
+  artifacts:
+    when: always
+    paths:
+      - htmlcov/
+      - coverage.xml
+    reports:
+      coverage_report:
+        coverage_format: cobertura
+        path: coverage.xml
+
+# -------------------------
+# Publish to PyPI (Trusted Publisher / OIDC)
+# -------------------------
+publish:pypi:
+  stage: publish
+  # Build/publish once (pick a stable version for publishing)
+  variables:
+    PYTHON_VERSION: "3.12"
+  rules:
+    # Typical choice: publish only for tags
+    - if: $CI_COMMIT_TAG
+  # Request an OIDC token from GitLab with the audience expected by PyPI ("pypi")
+  # This matches PyPI's GitLab Trusted Publishing guidance.
+  id_tokens:
+    PYPI_ID_TOKEN:
+      aud: pypi
+  environment:
+    name: 'release'
+    url: 'https://pypi.org/project/uvrev'
+  script:
+    # If your tooling expects CI_JOB_JWT_V2, map the token (safe no-op if unused).
+    - export CI_JOB_JWT_V2="$PYPI_ID_TOKEN"
+
+    # Build distributions
+    - uv build
+
+    # Publish using Trusted Publishing (OIDC). No API token needed if PyPI Trusted Publisher is configured.
+    - uv publish --trusted-publishing=always
+  artifacts:
+    when: always
+    paths:
+      - dist/

uvrev-0.1/.pre-commit-config.yaml

@@ -0,0 +1,56 @@
+repos:
+  - repo: local
+    hooks:
+      - id: ruff-format
+        name: ruff format
+        entry: uv run ruff format .
+        language: system
+        pass_filenames: false
+
+      - id: ruff-fix
+        name: ruff fix
+        entry: uv run ruff check --fix --quiet --exit-zero .
+        language: system
+        pass_filenames: false
+
+      - id: ruff-check
+        name: ruff check
+        entry: uv run ruff check .
+        language: system
+        pass_filenames: false
+
+      - id: mypy
+        name: mypy
+        entry: uv run mypy .
+        language: system
+        pass_filenames: false
+
+      # Run doctests under coverage (no reports yet; just collect data)
+      - id: pytest-doctest
+        name: pytest (doctest src)
+        entry: uv run coverage run --parallel-mode --source=src -m pytest --doctest-modules src
+        language: system
+        pass_filenames: false
+
+      # Run tests under coverage (no reports yet; just collect data)
+      - id: pytest-tests
+        name: pytest (tests)
+        entry: uv run coverage run --parallel-mode --source=src -m pytest tests
+        language: system
+        pass_filenames: false
+
+      # Combine + always output coverage + always generate HTML + enforce minimum
+      # Runs alone AFTER all other hooks (pre-commit will not run it concurrently).
+      - id: coverage-report
+        name: coverage (combine, html, report, fail-under)
+        entry: >
+          bash -c
+          'uv run coverage combine &&
+           uv run coverage html --fail-under=0 &&
+           uv run coverage xml --fail-under=0 &&
+           uv run coverage report --show-missing'
+        language: system
+        verbose: true
+        pass_filenames: false
+        require_serial: true
+

uvrev-0.1/.python-version

@@ -0,0 +1 @@
+3.12

uvrev-0.1/PKG-INFO

@@ -0,0 +1,136 @@
+Metadata-Version: 2.4
+Name: uvrev
+Version: 0.1
+Summary: uv env manager to enable conda-style revision tracking
+Author-email: Carli* Freudenberg <kound@posteo.de>
+License-Expression: MIT
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Natural Language :: English
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Programming Language :: Python :: Implementation :: PyPy
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Requires-Dist: click>=8
+Requires-Dist: platformdirs>=4
+Requires-Dist: tomlkit>=0.13
+Description-Content-Type: text/markdown
+
+# uvrev
+
+**uvrev** is a CLI tool that wraps the **uv** package manager and adds **git-based, conda-style revision tracking** for Python environments.
+
+It allows you to manage UV projects as isolated environments with a full, inspectable revision history. Every package change (add, remove, update) creates a new Git commit and tag, making it easy to understand what changed and to roll back to any previous state.
+
+---
+
+## Overview
+
+- Manage UV environments with automatic revision tracking
+- Track dependency changes over time using Git
+- Restore environments to any previous revision
+- Inspect package history in a familiar conda-style format
+
+Each environment is stored as a Git repository. Dependency changes are committed automatically, providing a complete and auditable history of your environment state.
+
+---
+
+## Installation
+
+### Prerequisites
+
+- `git`
+- `uv`
+
+### Install with uv
+
+```bash
+uv tool install uvrev
+```
+
+After installation, ensure that `uvrev` is available on your `PATH`:
+
+```bash
+uvrev --help
+```
+
+---
+
+## Key Features
+
+- Conda-style revision history showing added, removed, and updated packages
+- Git-based storage with automatic commits and tags
+- Rollback to any previous revision
+- Detailed changelog tracking both dependencies and pinned versions
+
+---
+
+## Commands
+
+| Command            | Description |
+|--------------------|-------------|
+| `uvrev env create` | Create a new UV project with revision tracking |
+| `uvrev env list`   | List all UV projects |
+| `uvrev add`        | Add packages to the current project |
+| `uvrev remove`     | Remove packages from the current project |
+| `uvrev sync`       | Sync project dependencies |
+| `uvrev list`       | List installed packages in the current environment |
+| `uvrev history`    | Show revision history with package changes |
+| `uvrev restore`    | Restore project to a specific revision |
+| `uvrev path`       | Show the path to the current project |
+| `uvrev run`        | Run uv commands in the project |
+
+---
+
+## Environment Selection
+
+`uvrev` determines the active environment based on the **currently activated virtual environment**.
+
+Activate an environment as usual:
+
+```bash
+source .venv/bin/activate
+```
+
+Once activated, all `uvrev` commands operate on that environment automatically. No additional flags or environment variables are required.
+
+This mirrors standard Python workflows and avoids implicit global state.
+
+---
+
+## Examples
+
+```bash
+uvrev env create myproject --python 3.12
+
+# activate venv
+source "$(uvrev path -e myproject)/.venv/bin/activate"
+
+uvrev add pandas numpy
+uvrev add requests
+
+uvrev list
+uvrev history
+uvrev restore 3
+uvrev run pip list
+```
+
+---
+
+## Why uvrev?
+
+`uvrev` combines the speed and simplicity of **uv** with the safety and transparency of **Git**, giving you:
+
+- Reproducible environments
+- Clear insight into dependency changes
+- Confidence to experiment, knowing you can always roll back

uvrev-0.1/README.md

@@ -0,0 +1,108 @@
+# uvrev
+
+**uvrev** is a CLI tool that wraps the **uv** package manager and adds **git-based, conda-style revision tracking** for Python environments.
+
+It allows you to manage UV projects as isolated environments with a full, inspectable revision history. Every package change (add, remove, update) creates a new Git commit and tag, making it easy to understand what changed and to roll back to any previous state.
+
+---
+
+## Overview
+
+- Manage UV environments with automatic revision tracking
+- Track dependency changes over time using Git
+- Restore environments to any previous revision
+- Inspect package history in a familiar conda-style format
+
+Each environment is stored as a Git repository. Dependency changes are committed automatically, providing a complete and auditable history of your environment state.
+
+---
+
+## Installation
+
+### Prerequisites
+
+- `git`
+- `uv`
+
+### Install with uv
+
+```bash
+uv tool install uvrev
+```
+
+After installation, ensure that `uvrev` is available on your `PATH`:
+
+```bash
+uvrev --help
+```
+
+---
+
+## Key Features
+
+- Conda-style revision history showing added, removed, and updated packages
+- Git-based storage with automatic commits and tags
+- Rollback to any previous revision
+- Detailed changelog tracking both dependencies and pinned versions
+
+---
+
+## Commands
+
+| Command            | Description |
+|--------------------|-------------|
+| `uvrev env create` | Create a new UV project with revision tracking |
+| `uvrev env list`   | List all UV projects |
+| `uvrev add`        | Add packages to the current project |
+| `uvrev remove`     | Remove packages from the current project |
+| `uvrev sync`       | Sync project dependencies |
+| `uvrev list`       | List installed packages in the current environment |
+| `uvrev history`    | Show revision history with package changes |
+| `uvrev restore`    | Restore project to a specific revision |
+| `uvrev path`       | Show the path to the current project |
+| `uvrev run`        | Run uv commands in the project |
+
+---
+
+## Environment Selection
+
+`uvrev` determines the active environment based on the **currently activated virtual environment**.
+
+Activate an environment as usual:
+
+```bash
+source .venv/bin/activate
+```
+
+Once activated, all `uvrev` commands operate on that environment automatically. No additional flags or environment variables are required.
+
+This mirrors standard Python workflows and avoids implicit global state.
+
+---
+
+## Examples
+
+```bash
+uvrev env create myproject --python 3.12
+
+# activate venv
+source "$(uvrev path -e myproject)/.venv/bin/activate"
+
+uvrev add pandas numpy
+uvrev add requests
+
+uvrev list
+uvrev history
+uvrev restore 3
+uvrev run pip list
+```
+
+---
+
+## Why uvrev?
+
+`uvrev` combines the speed and simplicity of **uv** with the safety and transparency of **Git**, giving you:
+
+- Reproducible environments
+- Clear insight into dependency changes
+- Confidence to experiment, knowing you can always roll back