Quickly create and compare sample objects.
Chide’s philosophy is to give you a simple registry of parameters needed to instantiate objects for your tests. There’s also support for simplifying objects down to mappings of their attributes for easier comparison and rendering, along with parsing and rendering of formats for inserting or asserting about multiple objects that are naturally tabular.
Quickstart
Say we have two classes that each require two parameters in order to be instantiated:
from dataclasses import dataclass
@dataclass
class ClassOne:
x: int
y: int
@dataclass
class ClassTwo:
a: int
b: ClassOneWe can set up a registry of sample values as follows:
from chide import Collection, nest
samples = Collection({
ClassOne: {'x': 1, 'y': 2},
ClassTwo: {'a': 1, 'b': nest(ClassOne)},
})Now we can quickly make sample objects:
>>> samples.make(ClassOne) ClassOne(x=1, y=2)
We can provide our own overrides if we want:
>>> samples.make(ClassOne, y=3) ClassOne(x=1, y=3)
We can also create nested trees of objects:
>>> samples.make(ClassTwo) ClassTwo(a=1, b=ClassOne(x=1, y=2))
1 maintainer
Metadata
1 maintainer
Release files for chide 4.0.0
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 | |
|---|---|---|---|---|
| chide-4.0.0.tar.gz | 32.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chide-4.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 45.1 kB
Release files / chide-4.0.0.tar.gz
| Download URL | chide-4.0.0.tar.gz |
|---|---|
| Size | 32.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
499b379fff482a0b507f91b78d704791ca10089299c2473d49cf4f46d2fe0347
|
|
BLAKE2b-256 checksum How to use checksums |
daa0d3c33e24f38bba2642c4e712cae183764414688cc9d55baf9bedf40e7acb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 14, 2026.
Transparency logRelease files / chide-4.0.0-py3-none-any.whl
| Download URL | chide-4.0.0-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
76804db9ad4c66cb4cc38564efa87013750817f18139d84be05940c931375222
|
|
BLAKE2b-256 checksum How to use checksums |
481d5e9aea0dda196fb5852989531533f54e6f465463fae63d2147b5e544784f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 14, 2026.
Transparency logSecurity for chide 4.0.0
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 chide-4.0.0.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 Mar 14, 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.
