jsonpit 4.5.0__tar.gz → 4.5.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,4 +1,4 @@
1
- # jsonpit API Reference (v4.5.0)
1
+ # jsonpit API Reference (v4.5.1)
2
2
 
3
3
  This document provides a foldable, searchable reference for the public `jsonpit` Python API. Designed for 100% C# JsonPit parity, zero third-party runtime dependencies, and Smalltalk-grade object-oriented architecture.
4
4
 
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: jsonpit
3
- Version: 4.5.0
3
+ Version: 4.5.1
4
4
  Summary: Daemon-free distributed storage over Cloud Drives for developers and AI agents — multi-process, immutable history, zero dependencies.
5
5
  Author: Dr. Rainer Burkhardt
6
6
  License-Expression: Apache-2.0
@@ -35,9 +35,9 @@ The canonical **reference (lead) implementation** is C# `JsonPit` and the `pits`
35
35
 
36
36
  ---
37
37
 
38
- ## Cross-Tool & Cross-Language Version Alignment (`v4.5.0`)
38
+ ## Cross-Tool & Cross-Language Version Alignment (`v4.5.1`)
39
39
 
40
- `jsonpit` and the `jpit` CLI are version-synchronized to **`v4.5.0`** in direct lockstep with C# `JsonPit` in [RAIkeep](https://github.com/Burkhardt/RAIkeep).
40
+ `jsonpit` and the `jpit` CLI are version-synchronized to **`v4.5.1`** in direct lockstep with C# `JsonPit` in [RAIkeep](https://github.com/Burkhardt/RAIkeep).
41
41
 
42
42
  ### Why Harmonized Versioning is Essential:
43
43
  - **Instant Compatibility Clarity:** Operators, DevOps pipelines, and autonomous AI agents immediately know whether `jpit` and `pits` share the exact same distributed protocol revision. If both tools report `4.4.x`, they guarantee identical master leasing rules, receipt mechanisms, 7-digit UTC timestamp parsing, and CR041 clean change file conventions.
@@ -106,7 +106,7 @@ pipx install jsonpit
106
106
  # (or via companion alias)
107
107
  pipx install jpit
108
108
 
109
- # Upgrade to the latest lockstep release (v4.5.0)
109
+ # Upgrade to the latest lockstep release (v4.5.1)
110
110
  pipx upgrade jsonpit
111
111
  # (or)
112
112
  pipx upgrade jpit
@@ -13,9 +13,9 @@ The canonical **reference (lead) implementation** is C# `JsonPit` and the `pits`
13
13
 
14
14
  ---
15
15
 
16
- ## Cross-Tool & Cross-Language Version Alignment (`v4.5.0`)
16
+ ## Cross-Tool & Cross-Language Version Alignment (`v4.5.1`)
17
17
 
18
- `jsonpit` and the `jpit` CLI are version-synchronized to **`v4.5.0`** in direct lockstep with C# `JsonPit` in [RAIkeep](https://github.com/Burkhardt/RAIkeep).
18
+ `jsonpit` and the `jpit` CLI are version-synchronized to **`v4.5.1`** in direct lockstep with C# `JsonPit` in [RAIkeep](https://github.com/Burkhardt/RAIkeep).
19
19
 
20
20
  ### Why Harmonized Versioning is Essential:
21
21
  - **Instant Compatibility Clarity:** Operators, DevOps pipelines, and autonomous AI agents immediately know whether `jpit` and `pits` share the exact same distributed protocol revision. If both tools report `4.4.x`, they guarantee identical master leasing rules, receipt mechanisms, 7-digit UTC timestamp parsing, and CR041 clean change file conventions.
@@ -84,7 +84,7 @@ pipx install jsonpit
84
84
  # (or via companion alias)
85
85
  pipx install jpit
86
86
 
87
- # Upgrade to the latest lockstep release (v4.5.0)
87
+ # Upgrade to the latest lockstep release (v4.5.1)
88
88
  pipx upgrade jsonpit
89
89
  # (or)
90
90
  pipx upgrade jpit
@@ -38,7 +38,7 @@ from .store import (
38
38
  parse_and_validate_seed_payload,
39
39
  )
40
40
 
41
- __version__ = "4.5.0"
41
+ __version__ = "4.5.1"
42
42
 
43
43
  __all__ = [
44
44
  "Pit",
@@ -2,6 +2,8 @@
2
2
  Domain exceptions for the jsonpit library.
3
3
  """
4
4
 
5
+ from __future__ import annotations
6
+
5
7
 
6
8
  class JsonPitError(Exception):
7
9
  """Base exception for all jsonpit domain errors."""
@@ -4,6 +4,8 @@ Encapsulates directory ecosystems, context manager transactions, distributed lea
4
4
  coordination, change-file streaming, receipt-based cleanup, and Mapping protocols.
5
5
  """
6
6
 
7
+ from __future__ import annotations
8
+
7
9
  import abc
8
10
  import copy
9
11
  from dataclasses import dataclass, field
@@ -913,6 +915,7 @@ class Pit(JsonPitBase, MutableMapping[str, PitItem], metaclass=PitMeta):
913
915
  new_data = old_item.to_dict()
914
916
  new_data["Id"] = new_key
915
917
  new_data.pop("Modified", None)
918
+ new_data.pop("Deleted", None)
916
919
  new_item = PitItem(new_data)
917
920
 
918
921
  with self._locker:
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
4
4
 
5
5
  [project]
6
6
  name = "jsonpit"
7
- version = "4.5.0"
7
+ version = "4.5.1"
8
8
  description = "Daemon-free distributed storage over Cloud Drives for developers and AI agents — multi-process, immutable history, zero dependencies."
9
9
  readme = "README.md"
10
10
  requires-python = ">=3.12"
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes