Sample
Define custom ParamType subclass to validate and convert custom argument types
sha256:b4f195835771a8dae96255c220a4c0d80574d657c4ae2c2ef51e5462b09d92cb
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 1
- Signing keys that built it
- 1
Declared environment
linux 24 · ubuntu · glibc 2.39 x64 pip
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| python 3.12 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · python@1python:3.12-alpine@sha256:d09d15e60962… |
2026-08-28 |
Case
HOW- Goal
- Define custom ParamType subclass to validate and convert custom argument types
- Packages
- Symbols
-
- click.ParamType
- click.ParamType.convert
- click.ParamType.fail
- click.ParamType.name
- Created
- 2026-08-28T04:13:15Z
Contract
- click.ParamType subclass defines name attribute for help synopsis
- convert() parses valid string arguments into custom Point coordinates
- convert() returns already instantiated Point objects without error
- invalid string formats call self.fail() which raises click.BadParameter and exits with code 2
- CliRunner captures parsed parameter values in command execution
Files
- NOTES.md
- PROMPT.md
- csx.json
- requirements.txt
- spec.json
- src/__init__.py
- src/cli.py
- test/contract.py
Origin Seeder
anonymous