Metadata-Version: 2.4
Name: pyvers
Version: 0.2.2
Summary: A Python library for managing multiple versions of dependencies
License: MIT
License-File: LICENSE
Author: vmoens
Author-email: vincentmoens@gmail.com
Requires-Python: >=3.9
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.9
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
Description-Content-Type: text/markdown

# 🐦 pyvers

A Python library for dynamic dispatch based on module versions and backends.

## What can you do with pyvers?

- 🔄 Handle breaking changes between different versions of a library without cluttering your code 
- 🔀 Switch seamlessly between different backend implementations (e.g., CPU vs GPU)
- ✨ Support multiple versions of a dependency in the same codebase without complex if/else logic 
- 🚀 Write version-specific optimizations while maintaining backward compatibility
- 🧹 Keep your code clean and maintainable while supporting multiple environments

## Usage

pyvers lets you write version-specific implementations that are automatically selected based on the installed package version or backend. Here's a simple example using the **register API** (recommended):

```python
from pyvers import implement_for, register_backend, get_backend, set_backend

# Register numpy backend - you could register more than one backend!
register_backend(group="numpy", backends={"numpy": "numpy"})

# Define the function with @implement_for, then register version-specific implementations
@implement_for("numpy")
def create_mask(arr):
    """Create a boolean mask marking positive values."""
    raise NotImplementedError("No matching numpy version found")

# Function for NumPy < 2.0 (using bool8)
@create_mask.register(from_version=None, to_version="2.0.0")
def _(arr):
    np = get_backend("numpy")
    return np.array([x > 0 for x in arr], dtype=np.bool8)

# Function for NumPy >= 2.0 (using bool_)
@create_mask.register(from_version="2.0.0")
def _(arr):
    np = get_backend("numpy")
    return np.array([x > 0 for x in arr], dtype=np.bool_)

# The correct implementation is automatically chosen based on your NumPy version
result = create_mask([-1, 2, -3, 4])
print("NumPy result:", result)
```

The `.register()` API follows the same pattern as `functools.singledispatch`. Using `_` as the function name is a Python convention that linters recognize, so you don't need `# noqa` comments.

### Alternative: Traditional API

You can also use the traditional decorator pattern (requires `# noqa: F811` for linters):

```python
@implement_for("numpy", from_version=None, to_version="2.0.0")
def create_mask(arr):
    np = get_backend("numpy")
    return np.array([x > 0 for x in arr], dtype=np.bool8)

@implement_for("numpy", from_version="2.0.0")
def create_mask(arr):  # noqa: F811
    np = get_backend("numpy")
    return np.array([x > 0 for x in arr], dtype=np.bool_)
```

Check out the [examples](examples/) folder for more advanced use cases:
- Switching between NumPy and JAX.numpy backends
- Handling CPU (SciPy) vs GPU (CuPy) implementations
- Managing breaking changes in PyTorch 2.0
- Supporting both gym and gymnasium APIs

## Installation

```bash
pip install pyvers
```

## Features

### Version-based dispatch

Automatically select the right implementation based on package versions:
```python
@implement_for("torch")
def optimize_model(model):
    """Optimize a model using version-appropriate techniques."""
    raise NotImplementedError("No matching torch version")

@optimize_model.register(from_version="2.0.0")
def _(model):
    return torch.compile(model)  # Only available in PyTorch 2.0+

@optimize_model.register(from_version=None, to_version="2.0.0")
def _(model):
    return model  # Fallback for older versions
```

### Backend switching

Easily switch between different implementations:
```python
# Register both backends
register_backend(group="numpy", backends={
    "numpy": "numpy",
    "jax.numpy": "jax.numpy"
})

# Use context manager to switch backends
with set_backend("numpy", "jax.numpy"):
    result = your_function()  # Uses JAX
with set_backend("numpy", "numpy"):
    result = your_function()  # Uses NumPy
```

### Dynamic imports
Backends are imported only when needed, so you can have optional dependencies:
```python
register_backend(group="sparse", backends={
    "scipy.sparse": "scipy.sparse",        # CPU backend
    "cupyx.scipy.sparse": "cupyx.scipy.sparse"  # GPU backend - does NOT require cupy to be installed!
})
```

## Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

## Development

### Setup

1. Clone the repository
2. Install Poetry (package manager)
3. Install dependencies:
   ```bash
   poetry install
   ```

### Running Tests

```bash
poetry run pytest
```

This will run the test suite with coverage reporting.

### Code Quality

We use [Ruff](https://github.com/astral-sh/ruff) for linting and code formatting. Ruff combines multiple Python linters into a single fast, unified tool.

To check your code:
```bash
poetry run ruff check .
```

To automatically fix issues:
```bash
poetry run ruff check --fix .
```

Ruff is configured to:
- Follow PEP 8 style guide
- Sort imports automatically
- Check for common bugs and code complexity
- Target Python 3.12+

See `pyproject.toml` for the complete linting configuration.

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details. 

## Citation

pyvers was developped as part of [TorchRL](https://github.com/pytorch/rl).

