tina4-python 3.13.96__tar.gz → 3.13.97__tar.gz

{tina4_python-3.13.96 → tina4_python-3.13.97}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tina4-python
-Version: 3.13.96
+Version: 3.13.97
 Summary: Tina4 Python v3 — Zero-dependency, lightweight web framework
 Author-email: Andre van Zuydam <andrevanzuydam@gmail.com>
 License: MIT

{tina4_python-3.13.96 → tina4_python-3.13.97}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "tina4-python"
-version = "3.13.96"
+version = "3.13.97"
 description = "Tina4 Python v3 — Zero-dependency, lightweight web framework"
 authors = [
     {name = "Andre van Zuydam", email = "andrevanzuydam@gmail.com"}

{tina4_python-3.13.96 → tina4_python-3.13.97}/tina4_python/__init__.py

@@ -51,7 +51,7 @@ def _resolve_version() -> str:
     #
     # test_version_constant.py now asserts this literal equals the pyproject
     # version, so the release bump cannot leave it behind again.
-    return "3.13.95"
+    return "3.13.97"
 
 
 __version__ = _resolve_version()

{tina4_python-3.13.96 → tina4_python-3.13.97}/tina4_python/queue/kafka_backend.py

@@ -67,7 +67,22 @@ class KafkaBackend:
         return self._backend.size(self._topic)
 
     def purge(self, status: str = "completed"):
-        pass  # Kafka does not support purging
+        """Not performable on Kafka — raises naming the backend and the operation.
+
+        purge(status) removes jobs SELECTED BY STATUS. A Kafka log has no notion
+        of job status and cannot delete records on demand: a partition is read
+        in offset order and records leave only by retention. This used to be a
+        bare ``pass``, so a caller who ran purge() believed jobs were removed
+        when nothing happened (ADR-0022 invariant 6: a backend that cannot
+        perform an operation refuses by name, it never silently no-ops).
+        """
+        raise NotImplementedError(
+            "The kafka queue backend cannot perform purge(): Kafka has no notion "
+            "of job status to purge by — a log is read in offset order and "
+            "records leave only by retention. Returning without doing anything "
+            "would claim jobs were purged when none were. Configure topic "
+            "retention, or use the file or mongodb backend."
+        )
 
     def retry_failed(self, max_retries: int = None) -> int:
         """Not performable on Kafka — raises naming the backend and the operation.
@@ -159,7 +174,21 @@ class KafkaBackend:
         return True
 
     def clear(self) -> int:
-        return 0  # Kafka does not support topic purging without admin API
+        """Not performable on Kafka — raises naming the backend and the operation.
+
+        clear() empties the queue. A Kafka log cannot delete records on demand:
+        a partition is read in offset order and records leave only by retention.
+        This used to ``return 0``, which claimed the queue was emptied when it
+        was untouched — the silent no-op ADR-0022 invariant 6 forbids. Refusing
+        by name is the honest answer.
+        """
+        raise NotImplementedError(
+            "The kafka queue backend cannot perform clear(): Kafka has no notion "
+            "of job status and cannot delete records on demand — a log is read "
+            "in offset order and records leave only by retention. Returning 0 "
+            "would claim the queue was emptied when it was not. Configure topic "
+            "retention, or use the file or mongodb backend."
+        )
 
     def complete(self, job: Job):
         self._backend.acknowledge(self._topic, str(job.id))

{tina4_python-3.13.96 → tina4_python-3.13.97}/tina4_python/queue/rabbitmq_backend.py

@@ -75,8 +75,22 @@ class RabbitMQBackend:
         return self._backend.size(self._topic)
 
     def purge(self, status: str = "completed"):
-        if status == "pending":
-            self._backend.clear(self._topic)
+        """Not performable on RabbitMQ — raises naming the backend and the operation.
+
+        purge(status) removes jobs SELECTED BY STATUS. RabbitMQ cannot address
+        messages by status: ``basic.get`` pops the head of the queue and the
+        only bulk operation is ``queue.purge``, which empties the WHOLE live
+        queue regardless of status. This used to drain that queue on
+        ``purge("pending")``, destroying every pending job — the destructive
+        no-op ADR-0022 invariant 6 forbids. Refusing by name is the honest
+        answer.
+        """
+        raise NotImplementedError(
+            "The rabbitmq queue backend cannot perform purge(): RabbitMQ cannot "
+            "address messages by status (basic.get pops the head of the queue), "
+            "so a status-addressed purge would have to drain the entire live "
+            "queue and destroy pending work. Use the file or mongodb backend."
+        )
 
     def retry_failed(self, max_retries: int = None) -> int:
         """Not performable on RabbitMQ — raises naming the backend and the operation.
@@ -169,8 +183,20 @@ class RabbitMQBackend:
         return True
 
     def clear(self) -> int:
-        self._backend.clear(self._topic)
-        return 0
+        """Not performable on RabbitMQ — raises naming the backend and the operation.
+
+        clear() empties the queue. RabbitMQ cannot address messages by status,
+        so the only thing it could do is ``queue.purge`` the WHOLE live queue.
+        This used to do exactly that and ``return 0``, silently destroying every
+        pending job. Draining a live broker on a status-addressed clear is data
+        loss (ADR-0022 invariant 6), so it refuses by name instead.
+        """
+        raise NotImplementedError(
+            "The rabbitmq queue backend cannot perform clear(): RabbitMQ cannot "
+            "address messages by status (basic.get pops the head of the queue), "
+            "so a status-addressed clear would have to drain the entire live "
+            "queue and destroy pending work. Use the file or mongodb backend."
+        )
 
     def complete(self, job: Job):
         self._backend.acknowledge(self._topic, str(job.id))