warpzone-sdk 15.1.0__tar.gz → 15.1.0.dev1__tar.gz

{warpzone_sdk-15.1.0 → warpzone_sdk-15.1.0.dev1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: warpzone-sdk
-Version: 15.1.0
+Version: 15.1.0.dev1
 Summary: The main objective of this package is to centralize logic used to interact with Azure Functions, Azure Service Bus and Azure Table Storage
 Author: Team Enigma
 Author-email: enigma@energinet.dk

{warpzone_sdk-15.1.0 → warpzone_sdk-15.1.0.dev1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "warpzone-sdk"
-version = "15.1.0"
+version = "15.1.0.dev1"
 description = "The main objective of this package is to centralize logic used to interact with Azure Functions, Azure Service Bus and Azure Table Storage"
 authors = [{ name = "Team Enigma", email = "enigma@energinet.dk" }]
 requires-python = ">=3.10"

{warpzone_sdk-15.1.0 → warpzone_sdk-15.1.0.dev1}/warpzone/deltastorage/table.py

@@ -53,10 +53,8 @@ class Table:
         As the `Table`-class is lazily initialized,
         the `delta_table`-property is initialized on the first access
         and saved for future use to minimize overhead.
-        It is *important* that this property is only initialized within
-        a lock when doing concurrent reads/writes
-        and not initialized when creating the `Table`-object.
-        This is important because using the same instance can lead to transaction
+        It is *important* that this property is not initialized when creating
+        the `Table`-object, because using the same instance can lead to transaction
         issues in delta as DeltaTable uses metadata (transaction id) from
         the first time the object is instantiated.
         """