https://github.com/henryiii/check-sdist
Check to see if an SDist matches Git
https://github.com/henryiii/check-sdist
packaging python
Last synced: about 1 month ago
JSON representation
Check to see if an SDist matches Git
- Host: GitHub
- URL: https://github.com/henryiii/check-sdist
- Owner: henryiii
- License: bsd-3-clause
- Created: 2023-03-31T19:39:33.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2025-04-14T18:36:10.000Z (about 1 month ago)
- Last Synced: 2025-04-15T07:56:55.648Z (about 1 month ago)
- Topics: packaging, python
- Language: Python
- Homepage:
- Size: 151 KB
- Stars: 8
- Watchers: 2
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Contributing: .github/CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# check-sdist
[![Actions Status][actions-badge]][actions-link]
[![codecov][codecov-badge]][codecov-link]
[![PyPI version][pypi-version]][pypi-link]
[![PyPI platforms][pypi-platforms]][pypi-link]
Have you ever shipped broken SDists with missing files or possibly dirty SDists
with files that shouldn't have been there? Have you noticed that standards
compliant tools aren't making the same SDist that `flit build` is? Is hatchling
adding `.DSStore` files when you ship from your macOS? No matter what
build-backend you use, check-sdist can help!
Check-sdist builds an SDist and compares the contents with your Git repository
contents. It can even temporarily inject common junk files (like pycache files
or OS specific files) and help verify that those aren't getting bundled into
your SDist. If you are getting files you didn't expect or missing files you did
expect, consult your build backend's docs to see how to include or exclude
files.
### Quick start
To run with [pipx][]:
```console
$ pipx run check-sdist[uv]
```
Or, if you like [uv][] instead (faster):
```console
$ uvx check-sdist
```
You can add `--no-isolation` to disable build isolation (faster, but must
preinstall build dependencies), `--source-dir` to select a different source
directory to check, and `--inject-junk` to temporarily inject some common junk
files while running. You can select an installer for build to use with
`--installer=`, choices are `uv`, `pip`, or `uv|pip`, which will use uv if
available (the default).
If you need the latest development version:
```console
$ pipx run --spec git+https://github.com/henryiii/check-sdist check-sdist
```
### Pre-commit integration
To use the [pre-commit](https://pre-commit.com) integration, put this in your
`.pre-commit-config.yaml`:
```yaml
- repo: https://github.com/henryiii/check-sdist
rev: v1.2.0
hooks:
- id: check-sdist
args: [--inject-junk]
additional_dependencies: [] # list your build deps here
```
This requires your build dependencies, but in doing so, it can cache the
environment, making it quite fast. The installation is handled by pre-commit;
see [`pre-commit-uv`](https://pypi.org/p/pre-commit-uv) if you want to try to
optimize the initial setup. If uv is present (including in your
`additional_dependencies`), the build will be slightly faster, as uv is used to
do the build. If you don't mind slower runs and don't want to require a build
dependency listing:
```yaml
- repo: https://github.com/henryiii/check-sdist
rev: v1.2.0
hooks:
- id: check-sdist-isolated
args: [--inject-junk]
```
This one defaults to including `uv` in `additional_dependencies`; you shouldn't
have to specify anything else.
### Configuration
To configure, these options are supported in your `pyproject.toml` file:
```toml
[tool.check-sdist]
sdist-only = []
git-only = []
default-ignore = true
recurse-submodules = true
mode = "git"
build-backend = "auto"
```
You can add `.gitignore` style lines here, and you can turn off the default
ignore list, which adds some default git-only files.
By default, check-sdist recursively scans the contents of Git submodules, but
you can disable this behavior (e.g. to support older Git versions that don't
have this capability).
You can also select `mode = "all"`, which will instead check every file on your
system. Be prepared to ignore lots of things manually, like `*.pyc` files, if
you use this.
You can tell check-sdist to look for exclude lists for a specific build backend
with `build-backend`, or `"none"` to only use it's own exclude list. Build
backends supported are `"flit_core.buildapi"`, `"hatchling.build"`,
`"scikit_build_core.build"`, `"pdm.backend"`, `"maturin"`, and
`"poetry.core.masonry.api"`. The default, `"auto"`, will try to detect the build
backend if `build-system.build-backend` is set to a known value.
### See also
- [check-manifest](https://github.com/mgedmin/check-manifest): A (currently)
setuptools specific checker that can suggest possible ways to include/exclude
files.
- [Scientific Python Development Guide](https://learn.scientific-python.org/development/):
Guidelines on which this package was designed.
[actions-badge]: https://github.com/henryiii/check-sdist/workflows/CI/badge.svg
[actions-link]: https://github.com/henryiii/check-sdist/actions
[pypi-link]: https://pypi.org/project/check-sdist/
[pypi-platforms]: https://img.shields.io/pypi/pyversions/check-sdist
[pypi-version]: https://img.shields.io/pypi/v/check-sdist
[codecov-badge]: https://codecov.io/gh/henryiii/check-sdist/graph/badge.svg?token=noB2wxFVBr
[codecov-link]: https://codecov.io/gh/henryiii/check-sdist
[pipx]: https://pipx.pypa.io
[uv]: https://docs.astral.sh/uv