Metadata-Version: 2.4
Name: xapp-tools
Version: 0.3.0
Summary: A collection of tools for working with xapp-core packages.
Project-URL: Repository, https://bitbucket.org/xstudios/xapp-tools.git
Project-URL: Issues, https://bitbucket.org/xstudios/xapp-tools/issues
Project-URL: Changelog, https://bitbucket.org/xstudios/xapp-tools/src/master/HISTORY.md
Author-email: Tim Santor <tsantor@xstudios.com>
License-File: AUTHORS.md
License-File: LICENSE
Classifier: Development Status :: 5 - Production/Stable
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: Natural Language :: English
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Programming Language :: Python :: 3.14
Requires-Python: >=3.11
Requires-Dist: click>=8.0
Requires-Dist: rich>=14.0
Description-Content-Type: text/markdown

# xapp-tools

![Coverage](https://img.shields.io/badge/coverage-66.43%25-yellow)

## Purpose

`xapp-tools` is an installable package of reusable build and development tooling for Xapp-based Python projects.
Its role is to provide automation that is broadly useful across repositories, not app-specific behavior.

## Usage

```bash
uv add xapp-tools --dev
xapp-tools --help
```

Available commands:

- `api-snapshot` — capture a public API snapshot
- `check-version-source` — ensure no hardcoded `__version__` in package source
- `coverage-badge` — update the coverage badge in README
- `update-deps` — refresh all dependencies to their latest versions via `uv`
- `verify-dist` — verify wheel and sdist build artifacts
- `wheel-smoke` — smoke-test an installed wheel

## Reuse Policy

Tools in this package should be written so they can be reused in other Python projects with little or no modification.
When project values are needed, prefer metadata/config introspection (for example from `pyproject.toml`) over hardcoded constants.

## Scope Boundaries

Only generic tooling belongs in this package.

Allowed examples:

- Dependency maintenance helpers
- Packaging/public API verification scripts
- Repository metadata utilities
- Generic release/build checks

Not allowed examples:

- Application/domain business logic
- Project feature commands
- One-off scripts tightly coupled to a specific app's runtime behavior
