Measles
Continuous cookiecutter featuring mise.
Bootstrap
cat <<'EOF' > .cookiecutter.yaml
default_context:
languages: Node,Python
python_dependencies:
- django
- gunicorn
EOF
mise use --global uv@latest
uvx cookiecutter --config-file .cookiecutter.yaml --no-input --overwrite-if-exists https://github.com/biobuddies/measles.git
mise trust --yes
mise install
mise pre-commit-all
mise test
Autoformat excludes
To exclude files from autoformatting and linting, add extended regular expressions
for relative paths from the repository root to .config/autoformat-excludes like:
^public/bundle\.min\.js$
^publickey\.asc$
Agent sandboxes
Set environment setup script to
grep -qs 'setup\.bash' .claude/hooks/session-start.sh || measles/.config/setup.bash
This accommodates Claude Code on the web's different single and multiple repository startups. Always include measles in multiple repository sessions: they start in the parent directory, where only this script can run setup.
TODO re-test on Codex Cloud, probably leveraging .codex/setup.sh
1 maintainer
Metadata
1 maintainer
Release files for measles 2026.42.1
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 | |
|---|---|---|---|---|
| measles-2026.42.1.tar.gz | 68.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| measles-2026.42.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 73.5 kB
Release files / measles-2026.42.1.tar.gz
| Download URL | measles-2026.42.1.tar.gz |
|---|---|
| Size | 68.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf2726741ceb8a4415ef0faf3cc89f65d3f7aac6aec5d59a1e1bd65a186f5879
|
|
BLAKE2b-256 checksum How to use checksums |
c1682a2b54829876df1c3d6604f69af707e142aeaadccea18a72ecfb83601b60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / measles-2026.42.1-py3-none-any.whl
| Download URL | measles-2026.42.1-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3391de83e5b2b25ccf0f68f02b7d611131585cca045ec96a61d5bc299b5822c3
|
|
BLAKE2b-256 checksum How to use checksums |
d4490cffd209a07f0968df39f03463fb2ecbc7d66df0dbb2cd7473aa6d5ac649
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for measles 2026.42.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for measles-2026.42.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA 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.
