sectionate
A package to sample grid-consistent sections from ocean model outputs
(Currently only supports structured grids.)
Quick Start Guide
For users: minimal installation within an existing environment
conda install -c conda-forge sectionate
For developers: installing dependencies from scratch using conda
git clone https://github.com/MOM6-community/sectionate.git
cd sectionate
conda env create -f docs/environment.yml
conda activate docs_env_sectionate
pip install -e .
python -m ipykernel install --user --name docs_env_sectionate --display-name "docs_env_sectionate"
jupyter-lab
Releasing
The git tag is the version. sectionate has no version string checked into
the source tree: hatch-vcs derives it from the tag at build time and writes
sectionate/_version.py (gitignored, but shipped inside the sdist and wheel).
To cut a release you tag; there is no file to bump and nothing to keep in sync.
- Make sure
masteris green and has everything you want in the release. - Publish a GitHub Release whose tag is
vX.Y.Z, targeting the commit you want to ship:gh release create vX.Y.Z --target "$(git rev-parse origin/master)" \ --title vX.Y.Z --generate-notes
Publishing it (not merely pushing a tag) is what fires the workflow. Target the commit you actually want: a tag placed before the commit you meant to release builds the previous version, and PyPI rejects it as a duplicate. - The Publish to PyPI workflow builds from that tag and uploads. It checks
out with
fetch-depth: 0so the tag is visible tohatch-vcs, and asserts that the built version matches the tag before publishing. - Verify: https://pypi.org/project/sectionate/.
- conda-forge builds from the PyPI sdist and lags by design; the autotick bot
opens the version-bump PR. Its recipe must list
hatch-vcsalongsidehatchlinginhost, since it builds with--no-build-isolation.
Two things follow from the tag being the version. Never add a version literal
back to the tree — sectionate/version.py is a shim over the generated file, and
a 0.0.0+unknown from it means the package was imported without being built or
installed, not that a number is missing. And any checkout that installs the
package needs its tags: a shallow clone, or a fork that never fetched them,
resolves a .devN version instead of the release line. That is why CI checks out
with fetch-depth: 0 and Read the Docs unshallows in post_checkout.
Metadata
Release files for sectionate 0.3.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sectionate-0.3.4.tar.gz | 37.8 kB | Without provenance | Details for sectionate-0.3.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sectionate-0.3.4-py3-none-any.whl | Python 3 | none | any | Details for sectionate-0.3.4-py3-none-any.whl |
Total release size: 74.8 kB
Release files / sectionate-0.3.4.tar.gz
| Download URL | sectionate-0.3.4.tar.gz |
|---|---|
| Size | 37.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb776bd9108dc056967dbb13bbc4b2dd7b240fc77d66ecd1ddcee987ec7a7320
|
|
BLAKE2b-256 checksum How to use checksums |
39c8c7c828ae2223cab39aeebd0109ab42c8a2002366d4d53dba8f4f32b929b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / sectionate-0.3.4-py3-none-any.whl
| Download URL | sectionate-0.3.4-py3-none-any.whl |
|---|---|
| Size | 36.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d842c9c1a11d5c6e0fe88cc3ac1e0931a7f489fb70afea7d927b5dd3ab141fb9
|
|
BLAKE2b-256 checksum How to use checksums |
4bd22cedfa66e02db9be28bfde32d795ea9159d3fca91d5d1eee51a1d1513fa5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for sectionate 0.3.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.