accordsync-core
Accord's merge core for Python: hybrid logical clocks, operations and the four merge strategies.
Pure Python, no I/O, no dependencies. Most programs use the client
accordsync or the server
accordsync-server, which depend on it. Python 3.11+.
pip install accordsync-core
| Strategy | Merges by |
|---|---|
lww() |
Highest hybrid logical clock wins. |
counter() |
Sum of every increment; none is ever lost. |
set_() |
Add-wins set: a remove only removes what its writer had seen. |
conflict() |
Concurrent values are all kept and the field is flagged; a resolution supersedes exactly the values its writer saw. |
set_() has a trailing underscore so it does not shadow Python's set.
import time
from accordsync_core import LocalWriter, conflict, counter, define_schema
schema = define_schema({"dossier": {"visits": counter(), "status": conflict()}})
def now() -> int:
return time.time_ns() // 1_000_000
a = LocalWriter(schema, "phone-a", now)
b = LocalWriter(schema, "phone-b", now)
# Each device writes offline...
from_a = [a.inc("dossier:1", "visits", 1), a.assign("dossier:1", "status", "approved")]
from_b = [b.inc("dossier:1", "visits", 2), b.assign("dossier:1", "status", "rejected")]
# ...then they exchange ops, in any order, as often as the network repeats them.
for op in from_b + from_b:
a.receive(op)
for op in reversed(from_a):
b.receive(op)
assert a.replica.snapshot() == b.replica.snapshot()
print(a.replica.read("dossier:1"))
# {'visits': 3, 'status': {'conflicted': [{'value': 'approved', 'opId': 'phone-a:2'},
# {'value': 'rejected', 'opId': 'phone-b:2'}]}}
It merges byte for byte like @accordsync/core:
the test suite runs the shared golden vectors in every delivery order, and random scenarios
generated by the TypeScript core must produce identical snapshots here.
Docs: accord.benhattab.pro/docs/schema · Source: crossben/accordsync-python · Licence: Apache-2.0
Metadata
Release files for accordsync-core 0.3.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 | |
|---|---|---|---|
| accordsync_core-0.3.1.tar.gz | 27.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| accordsync_core-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 50.7 kB
Release files / accordsync_core-0.3.1.tar.gz
| Download URL | accordsync_core-0.3.1.tar.gz |
|---|---|
| Size | 27.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bd69c2ee7a55ed9441e04a7e394dd4d59c4d137cb0096289ee8f5bd99201deb6
|
|
BLAKE2b-256 checksum How to use checksums |
4e69dc1e64035f102454aff579ab423aa7368956939662d4be826fc139472e8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 8, 2026.
Transparency logRelease files / accordsync_core-0.3.1-py3-none-any.whl
| Download URL | accordsync_core-0.3.1-py3-none-any.whl |
|---|---|
| Size | 23.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
31ad1302f2bb449d9be90fef0c80c92755b169f435b6ef754992c11691e13515
|
|
BLAKE2b-256 checksum How to use checksums |
94d338322194c940b4461bf2eaef576e6be6b2e9d6a7c11c2bb92369bc407a23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 8, 2026.
Transparency log