tracked-dict
Dict and list wrappers that track key access for reporting unconsumed data.
Wrap a parsed JSON/YAML/TOML structure in TrackedDict, read what you need
through normal dict access, then call unaccessed() to get dotted paths for
every key that was never touched.
Install
pip install tracked-dict
Usage
import json
from tracked_dict import TrackedDict
with open("config.json") as f:
data = TrackedDict(json.load(f))
name = data["project"]["name"]
version = data["project"]["version"]
for path in data.unaccessed():
print(f" unhandled: {path}")
API
TrackedDict(data: dict, _path: str = "")
d[key]/d.get(key, default)— read access; markskeyas accessedkey in d,len(d),bool(d),iter(d)— standard container ops (do not mark accessed)d.keys()— returns keys (does not mark accessed)d.values()/d.items()— iterate with wrapping; marks all keys accessedd.raw— the underlying plaindictd.mark_accessed(*keys)— explicitly mark keysd.mark_all_accessed()— mark every key at this leveld.unaccessed()— sorted list of dotted paths for all unaccessed keys, recursivelyd.accessed_keys()— set of keys accessed at this level
Nested dicts are automatically wrapped in TrackedDict, nested lists in TrackedList.
TrackedList(data: list, _path: str = "")
lst[i],len(lst),bool(lst),iter(lst)— standard accesslst.raw— the underlying plainlistlst.unaccessed()— collects unaccessed paths from wrapped children
How it works
When you access a key via [] or .get(), TrackedDict records that key.
Nested dicts and lists are lazily wrapped on first access so their keys are
tracked too. After your parser finishes, unaccessed() walks the tree and
returns dotted paths (e.g. "server.timeout", "users[0].email") for
anything never read.
This catches both parser omissions (data present but ignored) and unknown user-supplied fields — without maintaining a separate list of expected keys.
License
MIT
Metadata
Release files for tracked-dict 0.1.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 | Actions |
|---|---|---|---|---|
| tracked_dict-0.1.0.tar.gz | 7.0 kB | Without provenance | Details for tracked_dict-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tracked_dict-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for tracked_dict-0.1.0-py3-none-any.whl |
Total release size: 12.0 kB
Release files / tracked_dict-0.1.0.tar.gz
| Download URL | tracked_dict-0.1.0.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0962eeb9b2d0ee577b00010fc8315d0f4b9ba59c470eefa4211e1a2dcfb61fec
|
|
BLAKE2b-256 checksum How to use checksums |
9b8826808999945e7338e85fa82e3edfafc3dd26814b8b8918aa2bae47cf6436
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / tracked_dict-0.1.0-py3-none-any.whl
| Download URL | tracked_dict-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
956f548d9c91408d0c64c5c1cdbf24a57275e333ba493b9647c16a7dc4bd19da
|
|
BLAKE2b-256 checksum How to use checksums |
17e539dd27beaeeb0f9ffd08cbfeed432baa273632cf7aaae304fb30c9f29e76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for tracked-dict 0.1.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.
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.