This module is intended to ease access to nested data structures—in any combination of key or attribue access to each level of a hierarchy—where many paths in the tree may be missing. Typically, such data is encountered in semi-structured formats like JSON, YAML, or some XML, that is deserialized into Python data structures.
PEP 505 attempts to address this need with the addition of a number of new syntactic operators for attribute or item access where a special type of failure mode “coalesces” None values. Other libraries such as PyMaybe (https://pymaybe.readthedocs.io) perform a similar operation, and are more mature and robust.
On the other hand, by utilizing wrapt.ObjectProxy, this simple module manages to do some pretty neat stuff that even PyMaybe does not.
In this library, I simply want to provide simple wrapper classes that provide both what I think is more useful behavior and behavior that is semantically equivalent to PEP 505.
Classes:
GreedyAccess:
Wrap an object so that nested attribute and item access simply does not fail, but propagates a wrapped object across such nested access.
NullCoalesce:
Wrap an object so that encountering a None (or other indicated sentinel) at any level stops accessing further attributes and unboxes as a None (or other sentinel).
Aliased as NoneCoalesce
Metadata
Release files for coalescing 0.1.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 | Actions |
|---|---|---|---|---|
| coalescing-0.1.1.tar.gz | 2.7 kB | Without provenance | Details for coalescing-0.1.1.tar.gz |
Release files / coalescing-0.1.1.tar.gz
| Download URL | coalescing-0.1.1.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5319c2f556c250d49283d08380664990366d437183f3149c9e9e28f84e2b71b9
|
|
BLAKE2b-256 checksum How to use checksums |
f3f4120f04cc59f9fa8c55c711b67f1c9c34d8a59c34cd69249e6ff61b098987
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for coalescing 0.1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.