mathjson-solver 1.20.0__tar.gz → 1.20.1__tar.gz

{mathjson_solver-1.20.0 → mathjson_solver-1.20.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mathjson-solver
-Version: 1.20.0
+Version: 1.20.1
 Summary: Utilities for MathJSON evaluation
 Project-URL: Homepage, https://github.com/LongenesisLtd/mathjson-solver
 Project-URL: Bug Tracker, https://github.com/LongenesisLtd/mathjson-solver/issues

{mathjson_solver-1.20.0 → mathjson_solver-1.20.1}/SECURITY.md

@@ -5,8 +5,8 @@
 
 | Version | Supported          |
 | ------- | ------------------ |
-| 1.13.x   | :white_check_mark: |
-| < 1.13.x   | :x:                |
+| 1.20.x   | :white_check_mark: |
+| < 1.20.x   | :x:                |
 
 
 ## Reporting a Vulnerability

{mathjson_solver-1.20.0 → mathjson_solver-1.20.1}/docs/README.md

@@ -327,7 +327,7 @@ If a constant definition raises an exception (e.g. because a referenced paramete
 # Result: 11.25  (c_old was never needed)
 ```
 
-A constant that failed to compute can be detected with `["Equal", "c_old", None]`.
+A constant that failed to compute resolves to `None`, which is falsy. Use `["IsFalse", "c_old"]` to detect it (or `["IsTrue", "c_old"]` to confirm it computed successfully).
 
 ### If Statement
 ```
@@ -824,7 +824,7 @@ The logical complement of `IsDefined`. Returns `True` if the name is not defined
 ["Constants", ["x", 5], ["IsUndefined", "y"]]   # True
 ```
 
-Note: when a `Constants` definition raises an exception, that constant is set to `None` (see null-propagation below). In that case `IsUndefined` still returns `False` — the name is defined, just with a `None` value. Use `["Equal", "val", None]` to test for that explicitly.
+Note: when a `Constants` definition raises an exception, that constant is set to `None` (see null-propagation below). In that case `IsUndefined` still returns `False` — the name is defined, just with a `None` value. Use `["IsFalse", "val"]` to detect a failed constant (since `None` is falsy).
 
 ---
 

{mathjson_solver-1.20.0 → mathjson_solver-1.20.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "mathjson-solver"
-version = "1.20.0"
+version = "1.20.1"
 authors = [{name = "Martins Mednis", email = "mrt@mednis.info"}]
 description = "Utilities for MathJSON evaluation"
 readme = "README.md"

{mathjson_solver-1.20.0 → mathjson_solver-1.20.1}/src/mathjson_solver/__main__.py

@@ -617,6 +617,8 @@ def create_mathjson_solver(solver_parameters):
 
             def Strftime(s):
                 dt = _try_parse_datetime(f(s[1], c))
+                if not isinstance(dt, (datetime.datetime, datetime.date)):
+                    raise ValueError(f"Strftime: could not parse input as datetime: {dt!r}")
                 parameters = f(s[2], c)
                 return dt.strftime(parameters)
 

{mathjson_solver-1.20.0 → mathjson_solver-1.20.1}/tests/test_datetime.py

@@ -134,6 +134,20 @@ class TestStrftime:
         result = solver(["Strftime", "2025-06-15T14:30:45", "%Y-%m-%d %H:%M:%S"])
         assert result == "2025-06-15 14:30:45"
 
+    def test_strftime_raises_on_unparseable_input(self):
+        """Strftime must raise MathJSONException (not AttributeError) for unparseable input."""
+        from mathjson_solver import MathJSONException
+        solver = create_solver({})
+        with pytest.raises(MathJSONException):
+            solver(["Strftime", "not-a-date", "%Y-%m-%d"])
+
+    def test_strftime_raises_on_none_input(self):
+        """Strftime must raise MathJSONException when input resolves to None."""
+        from mathjson_solver import MathJSONException
+        solver = create_solver({})
+        with pytest.raises(MathJSONException):
+            solver(["Strftime", None, "%Y-%m-%d"])
+
 
 class TestDatetimeChaining:
     """Test complex datetime operation chains."""