metta-websocket 0.9.2__py3-none-any.whl

metta_websocket-0.9.2.dist-info/METADATA

@@ -0,0 +1,32 @@
+Metadata-Version: 2.4
+Name: metta-websocket
+Version: 0.9.2
+Summary: websocket-client's own timeouts, so an absent MeTTa backend reads as absent
+License-Expression: MIT
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3
+Classifier: Intended Audience :: Science/Research
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+Requires-Dist: pymetta==0.9.2
+Requires-Dist: websocket-client
+
+# metta-websocket
+
+websocket-client's own timeouts, so an absent MeTTa backend reads as absent.
+
+`pymetta` names no third-party library. This package is one row against the `transport-error` point, and the seat
+finds it exactly as it finds a package written by somebody else: through the
+`metta.extensions` entry point, loaded at the first dispatch that has no answer
+without it, or through `import metta_websocket`, whose module body registers the same
+rows.
+
+```sh
+pip install metta-websocket          # or: pip install 'pymetta[das]'
+```
+
+Its tests are in `tests/`, and they run in the workspace suite:
+
+```sh
+sh extensions/python/test.sh ext/metta-websocket
+```

metta_websocket-0.9.2.dist-info/RECORD

@@ -0,0 +1,6 @@
+metta_websocket.py,sha256=DmkyTHXjGNvZIy-3naSJWISevF0ax6HcPXHeEmU-BMI,1682
+metta_websocket-0.9.2.dist-info/METADATA,sha256=50u0iJKVNW3qawxjwiPZKkWfu7r3NeCV_DHhu8w_w9M,1103
+metta_websocket-0.9.2.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
+metta_websocket-0.9.2.dist-info/entry_points.txt,sha256=ElQEr2w7DAQyZU_jrE3YYU7GZ6hp3hnDMscto0WAPEw,53
+metta_websocket-0.9.2.dist-info/top_level.txt,sha256=DWf1SB0H8zq9pjxaoQ5IVjYDt12MRWxwrXKC80Ec2Kc,16
+metta_websocket-0.9.2.dist-info/RECORD,,

metta_websocket-0.9.2.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (84.0.0)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

metta_websocket-0.9.2.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[metta.extensions]
+metta-websocket = metta_websocket

metta_websocket-0.9.2.dist-info/top_level.txt

@@ -0,0 +1 @@
+metta_websocket

metta_websocket.py

@@ -0,0 +1,42 @@
+"""Purpose: websocket-client's own timeouts, so an absent backend reads as absent.
+
+`metta._errors.errors.is_transport_failure` asks whether a failure means the backend is
+ABSENT rather than wrong, which decides whether a client retries or reports.
+The obvious test does not separate them: a socket timeout raises OSError, but
+websocket-client's own timeout does NOT subclass it, so "is the cause an
+OSError" misses exactly the shape a broken event stream takes under load. One
+row against the seat's `transport-error` point says which classes those are.
+
+Installed beside pymetta, or through `pip install 'pymetta[das]'`. The row
+holds the module NAME and imports nothing; the classes are read only when a
+failure is actually classified, and only if websocket-client is imported.
+
+Assumes:
+  - the two exception classes keep their names, which is the only thing this
+    row knows about the library
+Guarantees:
+  - a websocket timeout and a closed stream both read as transport failures,
+    and an ordinary application error does not [tested: tests/test_websocket.py;
+    commit=94057a0f073c0fab0a35c42beff2c324d8a0addd]
+Open Obligations:
+  To Do: None
+  Hacks: None
+  Future Enhancements: None
+"""
+
+from __future__ import annotations
+
+from metta import seam
+
+
+def _classes(module) -> tuple[type[BaseException], ...]:
+    """websocket-client's own timeout and closed-stream exceptions."""
+    return (module.WebSocketTimeoutException, module.WebSocketConnectionClosedException)
+
+
+def register() -> None:
+    """This package's one row, against the seat's `transport-error` point."""
+    seam.transport_error.register("websocket", module="websocket", classes=_classes)
+
+
+register()