0.1.1: Update internal implementation of ThreadWithResult

- this release does not add any new functionality nor modify existing functionality - HOWEVER, if any existing code relied on any undocumented, implementation details of the previous `ThreadWithResult` implementation, the previous implementation can be accessed by doing something like ``` from save_thread_result import ___init__OverrideThreadWithResult as ThreadWithResult # code to use ThreadWithResult remains unchanged ``` - for an explanation about the changes to the `ThreadWithResult` implementation, see commit 7885b33
shailshouryya · May 30, 2023 · bf1b7f6 · bf1b7f6
1 parent 21bd027
commit bf1b7f6
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/python/save_thread_result/__init__.py b/python/save_thread_result/__init__.py
@@ -9,7 +9,7 @@
 from datetime import datetime
 
 
-__version__              = '0.1.0'
+__version__              = '0.1.1'
 
 
 _general_documentation = '''

diff --git a/python/setup.py b/python/setup.py
@@ -31,7 +31,7 @@
     # 3. MAINTENANCE version when they make backwards-compatible bug fixes.
     # Adopting this approach as a project author allows users to make use of “compatible release” specifiers, where name ~= X.Y requires at least release X.Y, but also allows any later release with a matching MAJOR version.
     # Python projects adopting semantic versioning should abide by clauses 1-8 of the Semantic Versioning 2.0.0 specification: https://semver.org/.
-    version                       = '0.1.0',
+    version                       = '0.1.1',
     name                          = 'save-thread-result',
     description                   = 'Simple subclass wrapper around `threading.Thread` to get the return value from a thread in python. Exact same interface as `threading.Thread`! 🌟 Star this repo if you found it useful! 🌟',
     long_description              = long_description,