The configurable-objects library contains classes and methods for registering handlers to make it easy for managing parameters of objects (not their entire state) to be easily retrieved/set via dictionaries and therefore also via a JSON representation.
Changelog
0.0.1 (2023-01-10)
initial release, migrated from python-weka-wrapper3
Metadata
Release files for configurable-objects 0.0.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 | |
|---|---|---|---|---|
| configurable-objects-0.0.1.tar.gz | 4.4 kB | Without provenance | Details |
Release files / configurable-objects-0.0.1.tar.gz
| Download URL | configurable-objects-0.0.1.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b115c9f42984b7f774c341543d6dfc60c080af236c4463e542e46fdfbe69521
|
|
BLAKE2b-256 checksum How to use checksums |
f3a2dd44a746ad232d9536ad163ce901df1eefff714c2a1c88e66102011af442
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Security for configurable-objects 0.0.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.
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.