requiresthat 2025.6.18.2__tar.gz → 2025.6.19.0__tar.gz

{requiresthat-2025.6.18.2 → requiresthat-2025.6.19.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: requiresthat
-Version: 2025.6.18.2
+Version: 2025.6.19.0
 Summary: Support for requirements-assisted development
 Author-email: Ann T Ropea <bedhanger@gmx.de>
 License-Expression: MIT
@@ -35,11 +35,16 @@ Example usage
     X = C(data='spam')
     X.method()
 
+See the `tests <https://gitlab.com/bedhanger/mwe/-/blob/master/python/requiresthat/tests/test_requiresthat.py>`_
+for more.
+
 The ``that`` can be almost any valid Python statement which can be evaluated and whose veracity can
 be asserted, and the result thereof will decide whether or not the method fires/will be considered a
 success.
 
-The parameter ``when`` decides if the condition is a-priori, post-mortem, or before-and-after.
+The parameter ``when`` decides if the condition is
+`a-priori, post-mortem, or before-and-after
+<https://gitlab.com/bedhanger/mwe/-/blob/master/python/requiresthat/src/_when.py>`_.
 The default is a-priori, meaning a precondition.  Note that before-and-after does *not* mean during;
 you cannot mandate an invariant this way!
 

{requiresthat-2025.6.18.2 → requiresthat-2025.6.19.0}/README.rst

@@ -26,11 +26,16 @@ Example usage
     X = C(data='spam')
     X.method()
 
+See the `tests <https://gitlab.com/bedhanger/mwe/-/blob/master/python/requiresthat/tests/test_requiresthat.py>`_
+for more.
+
 The ``that`` can be almost any valid Python statement which can be evaluated and whose veracity can
 be asserted, and the result thereof will decide whether or not the method fires/will be considered a
 success.
 
-The parameter ``when`` decides if the condition is a-priori, post-mortem, or before-and-after.
+The parameter ``when`` decides if the condition is
+`a-priori, post-mortem, or before-and-after
+<https://gitlab.com/bedhanger/mwe/-/blob/master/python/requiresthat/src/_when.py>`_.
 The default is a-priori, meaning a precondition.  Note that before-and-after does *not* mean during;
 you cannot mandate an invariant this way!
 

{requiresthat-2025.6.18.2 → requiresthat-2025.6.19.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "requiresthat"
-version = "2025.6.18.2"
+version = "2025.6.19.0"
 authors = [
     {name = "Ann T Ropea", email = "bedhanger@gmx.de"},
 ]

{requiresthat-2025.6.18.2 → requiresthat-2025.6.19.0}/src/requiresthat.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: requiresthat
-Version: 2025.6.18.2
+Version: 2025.6.19.0
 Summary: Support for requirements-assisted development
 Author-email: Ann T Ropea <bedhanger@gmx.de>
 License-Expression: MIT
@@ -35,11 +35,16 @@ Example usage
     X = C(data='spam')
     X.method()
 
+See the `tests <https://gitlab.com/bedhanger/mwe/-/blob/master/python/requiresthat/tests/test_requiresthat.py>`_
+for more.
+
 The ``that`` can be almost any valid Python statement which can be evaluated and whose veracity can
 be asserted, and the result thereof will decide whether or not the method fires/will be considered a
 success.
 
-The parameter ``when`` decides if the condition is a-priori, post-mortem, or before-and-after.
+The parameter ``when`` decides if the condition is
+`a-priori, post-mortem, or before-and-after
+<https://gitlab.com/bedhanger/mwe/-/blob/master/python/requiresthat/src/_when.py>`_.
 The default is a-priori, meaning a precondition.  Note that before-and-after does *not* mean during;
 you cannot mandate an invariant this way!