functionalthreading 1.0.3__tar.gz → 1.0.5__tar.gz

{functionalthreading-1.0.3 → functionalthreading-1.0.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: functionalthreading
-Version: 1.0.3
+Version: 1.0.5
 Summary: Concurrent functional programming with thread-based parallelism
 Author-email: Richard Tong <richytong@gmail.com>
 License-Expression: Unlicense
@@ -34,6 +34,12 @@ The functionalthreading module provides functions for concurrent functional prog
 ## Functional Programming
 See [Functional Programming HOWTO](https://docs.python.org/3/howto/functional.html).
 
+## Locking
+This module intentionally does not include any thread-locking mechanism, for example [Lock](https://docs.python.org/3/library/threading.html#threading.Lock). It is the responsibility of the programmer using this module to ensure that updates to shared state are atomic.
+
+## Atomicity
+Atomicity is the property of an update (transaction) that implies indivisible and irreducible. An atomic update to state is an indivisible and irreducible update to state. State could mean a log file, cache, database table, game engine physics state, operating system process tables, file system metadata, etc.
+
 ## Reference
 
 ### Thread(group=None, target=None, name=None, args=(), kwargs={}, *, daemon=None, context=None)

{functionalthreading-1.0.3 → functionalthreading-1.0.5}/README.md

@@ -19,6 +19,12 @@ The functionalthreading module provides functions for concurrent functional prog
 ## Functional Programming
 See [Functional Programming HOWTO](https://docs.python.org/3/howto/functional.html).
 
+## Locking
+This module intentionally does not include any thread-locking mechanism, for example [Lock](https://docs.python.org/3/library/threading.html#threading.Lock). It is the responsibility of the programmer using this module to ensure that updates to shared state are atomic.
+
+## Atomicity
+Atomicity is the property of an update (transaction) that implies indivisible and irreducible. An atomic update to state is an indivisible and irreducible update to state. State could mean a log file, cache, database table, game engine physics state, operating system process tables, file system metadata, etc.
+
 ## Reference
 
 ### Thread(group=None, target=None, name=None, args=(), kwargs={}, *, daemon=None, context=None)

{functionalthreading-1.0.3 → functionalthreading-1.0.5}/functionalthreading.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: functionalthreading
-Version: 1.0.3
+Version: 1.0.5
 Summary: Concurrent functional programming with thread-based parallelism
 Author-email: Richard Tong <richytong@gmail.com>
 License-Expression: Unlicense
@@ -34,6 +34,12 @@ The functionalthreading module provides functions for concurrent functional prog
 ## Functional Programming
 See [Functional Programming HOWTO](https://docs.python.org/3/howto/functional.html).
 
+## Locking
+This module intentionally does not include any thread-locking mechanism, for example [Lock](https://docs.python.org/3/library/threading.html#threading.Lock). It is the responsibility of the programmer using this module to ensure that updates to shared state are atomic.
+
+## Atomicity
+Atomicity is the property of an update (transaction) that implies indivisible and irreducible. An atomic update to state is an indivisible and irreducible update to state. State could mean a log file, cache, database table, game engine physics state, operating system process tables, file system metadata, etc.
+
 ## Reference
 
 ### Thread(group=None, target=None, name=None, args=(), kwargs={}, *, daemon=None, context=None)

{functionalthreading-1.0.3 → functionalthreading-1.0.5}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "functionalthreading"
-version = "1.0.3"
+version = "1.0.5"
 authors = [
   { name="Richard Tong", email="richytong@gmail.com" },
 ]