philiprehberger-dict-merge
Deep merge dictionaries safely with conflict resolution.
Installation
pip install philiprehberger-dict-merge
Usage
from philiprehberger_dict_merge import merge, Strategy
base = {"db": {"host": "localhost", "port": 5432}, "debug": False}
override = {"db": {"port": 3306, "name": "mydb"}, "debug": True}
merge(base, override)
# {"db": {"host": "localhost", "port": 3306, "name": "mydb"}, "debug": True}
# Multiple dicts
merge(defaults, config_file, env_overrides)
# Keep first value on conflict
merge(a, b, strategy=Strategy.KEEP_FIRST)
# Append lists instead of replacing
merge(a, b, list_strategy="append")
# Raise on conflict
from philiprehberger_dict_merge import MergeConflictError
try:
merge({"key": 1}, {"key": 2}, strategy=Strategy.ERROR)
except MergeConflictError as e:
print(e.key) # "key"
print(e.left) # 1
print(e.right) # 2
# Custom resolution per key
merge(
{"a": 1, "b": 5},
{"a": 4, "b": 2},
strategy=Strategy.CALLBACK,
on_conflict=lambda key, left, right: max(left, right),
)
# {"a": 4, "b": 5}
Flatten and unflatten
Convert between nested dicts and dot-notation flat dicts. Useful when merging config that arrives in different shapes.
from philiprehberger_dict_merge import flatten, unflatten
flatten({"db": {"host": "x", "port": 5432}})
# {"db.host": "x", "db.port": 5432}
unflatten({"db.host": "x", "db.port": 5432})
# {"db": {"host": "x", "port": 5432}}
# Round-trip
unflatten(flatten({"a": {"b": {"c": 1}}})) == {"a": {"b": {"c": 1}}}
API
| Function / Class | Description |
|---|---|
merge(*dicts, strategy=Strategy.REPLACE, list_strategy="replace") |
Deep merge |
Strategy.REPLACE |
Later values win (default) |
Strategy.KEEP_FIRST |
Earlier values win |
Strategy.ERROR |
Raise on conflict |
Strategy.CALLBACK |
Resolve conflicts via on_conflict(key, left, right) |
MergeConflictError |
Raised by Strategy.ERROR — has .key, .left, .right attributes |
List strategies: "replace", "append", "unique", "concat" |
List merge modes |
flatten(d, sep=".") |
Flatten a nested dict into separator-joined keys |
unflatten(d, sep=".") |
Reverse of flatten — expand separator-joined keys into nested dicts |
Development
pip install -e .
python -m pytest tests/ -v
Support
If you find this project useful:
License
Metadata
Release files for philiprehberger-dict-merge 0.3.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 |
|---|---|---|---|---|
| philiprehberger_dict_merge-0.3.0.tar.gz | 7.4 kB | Without provenance | Details for philiprehberger_dict_merge-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| philiprehberger_dict_merge-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for philiprehberger_dict_merge-0.3.0-py3-none-any.whl |
Total release size: 13.2 kB
Release files / philiprehberger_dict_merge-0.3.0.tar.gz
| Download URL | philiprehberger_dict_merge-0.3.0.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f8f181a05864104c6edf778ff659f1f573791015b41855b5ec2312ac64b0665
|
|
BLAKE2b-256 checksum How to use checksums |
0f1d2224f2e71415ff7ca5d981d91b410662ea2a3edfbb615c7951ea13057e49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / philiprehberger_dict_merge-0.3.0-py3-none-any.whl
| Download URL | philiprehberger_dict_merge-0.3.0-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3eafc990d7f135b42449f94f3703d1f13e9c8411d56c6b5eeadcb4fb0051a548
|
|
BLAKE2b-256 checksum How to use checksums |
d3f7d636d7f129ede0a3aa5e017efdf2169b68adb391fb170f8a9b1575b27eed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for philiprehberger-dict-merge 0.3.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.