robovast-client 2.1.0__py3-none-any.whl

robovast/client/__init__.py

@@ -0,0 +1,17 @@
+# Copyright (C) 2026 Frederik Pasch
+# SPDX-License-Identifier: Apache-2.0
+
+"""What a client needs to talk to a robovast-service, and nothing else.
+
+These modules were under :mod:`robovast.common`, which cannot host them once the client
+ships as its own distribution: ``common/__init__.py`` carries the lazy re-export map, so
+the package is a regular one and its contents cannot be split across two distributions.
+``robovast.client`` is a package of its own for exactly that reason.
+
+The rule for what belongs here is the install it has to survive in: ``pydantic``,
+``click`` and ``requests``, with no simulator, no Kubernetes client and no array library.
+Anything reaching further belongs in the core.
+
+Deliberately kept empty of re-exports. The parent it came from cost 528 modules to touch
+because its ``__init__`` imported eagerly; repeating that here would undo the point.
+"""

robovast/client/app_version.py

@@ -0,0 +1,65 @@
+# Copyright (C) 2026 Frederik Pasch
+# SPDX-License-Identifier: Apache-2.0
+
+"""The version of the code *this process is running*.
+
+Lives here rather than beside the in-process service because both sides of the version
+handshake need it: the HTTP client reports its own version, the service reports the one it
+loaded. Keeping it in ``local_transport`` meant a client could not ask "what am I running?"
+without importing the whole in-process server.
+"""
+
+from importlib.metadata import PackageNotFoundError
+from importlib.metadata import version as _pkg_version
+
+
+def running_version() -> str:
+    """The running code's version: git revision if available, else package metadata.
+
+    The preference is the point. A service is long-lived and loads its code once, so a
+    client needs to tell "the fix I just made is loaded" from "this process predates it".
+    The packaged version alone cannot — it stays ``2.0.0`` across every edit.
+
+    Never raises. The git-revision path needs ``robovast.common.execution``, which a
+    client-only install does not have, so the import is inside the ``try`` with everything
+    else: a version string is diagnostic, and failing to produce one must not break the
+    handshake it is part of.
+
+    The distributions are tried in order of how much they say about the running code:
+    ``robovast`` when it is installed, then ``robovast-client``, which is installed in
+    *every* case and so is the last answer that is still a fact. ``0.0.0+unknown`` remains
+    only for a source tree with no metadata at all — reported by a perfectly good
+    client-only install, it would read as a broken install rather than a small one.
+    """
+    try:
+        from robovast.common.execution import \
+            get_app_version  # pylint: disable=import-outside-toplevel
+        return get_app_version()
+    except Exception:  # noqa: BLE001 - version reporting must never break the handshake
+        for dist in ("robovast", "robovast-client"):
+            try:
+                return _pkg_version(dist)
+            except PackageNotFoundError:
+                continue
+        return "0.0.0+unknown"  # a source tree with no metadata
+
+
+def running_revision() -> str:
+    """The running code's git revision, or ``""`` when it cannot be determined.
+
+    The strict half of :func:`running_version`, and the reason both exist: a *version* is
+    allowed to fall back to package metadata, because "which robovast am I?" always has an
+    answer worth printing. A *revision* is not, because the only question it is asked is
+    "is this the same code as over there?" -- and a semver that stays ``2.0.0`` across every
+    edit answers that with a confident wrong yes.
+
+    ``""`` therefore means "no comparison is possible here", which a caller can act on by
+    saying so. Two cases produce it and neither is an error: a client-only install (no
+    ``robovast.common.execution`` to ask) and a non-git install of the full package.
+    """
+    try:
+        from robovast.common.execution import \
+            code_revision  # pylint: disable=import-outside-toplevel
+        return code_revision()
+    except Exception:  # noqa: BLE001 - a diagnostic must not raise; "" is the honest answer
+        return ""