l3io-wordpress-backup 1.0.0__py3-none-any.whl

l3io/wp/backup/__init__.py

@@ -0,0 +1,22 @@
+"""``l3io.wp.backup`` — WordPress backup, restore and relocation.
+
+This is the package root of the ``l3io-wordpress-backup`` distribution. ``l3io`` and
+``l3io.wp`` are a **PEP 420 native namespace** shared with ``l3io-wordpress-config``
+and ``l3io-wp-database``; neither carries an ``__init__.py`` (AD-27), and
+``tests/contracts/test_namespace_layout.py`` asserts that, in the source tree
+and in the built wheel.
+
+The public surface is declared by ``__all__`` (spine, Consistency
+Conventions). It is deliberately minimal at this stage: the packaging skeleton
+and its contract gates land before any behaviour, so that every gate is proven
+to fire before there is anything for it to catch.
+"""
+
+from __future__ import annotations
+
+__all__ = ["__version__"]
+
+# Re-exported from _version, which reads installed distribution metadata. There
+# used to be a literal here AND one in pyproject.toml, with nothing comparing
+# them; the git tag is now the only source.
+from l3io.wp.backup._version import __version__

l3io/wp/backup/_version.py

@@ -0,0 +1,31 @@
+"""The installed distribution's version, resolved at runtime.
+
+There is no version literal in this package. ``pyproject.toml`` declares the
+version ``dynamic`` with ``source = "vcs"``, so the tag is the single source and
+``hatch-vcs`` resolves it at build time into the distribution metadata. This
+module reads that metadata back, which keeps ``__version__`` importable without
+reintroducing a second value that could disagree with the tag.
+
+Deliberately NOT a generated file. A ``_version.py`` written by the build would
+be absent from a fresh clone and from an editable install done before the first
+build, so anything importing it would fail in exactly the situation a new
+contributor hits first.
+"""
+
+from __future__ import annotations
+
+from importlib.metadata import PackageNotFoundError
+from importlib.metadata import version as _dist_version
+
+__all__ = ["__version__"]
+
+#: Sentinel for "running from a tree that was never installed". It is a valid
+#: PEP 440 version and sorts BELOW every real release, so a build that somehow
+#: escapes with it cannot outrank a published one -- the same reasoning as the
+#: 0.1.devN fallback for an untagged tree: wrong in the safe direction.
+_UNKNOWN = "0.0.0+unknown"
+
+try:
+    __version__: str = _dist_version("l3io-wordpress-backup")
+except PackageNotFoundError:  # pragma: no cover - only when not installed
+    __version__ = _UNKNOWN

l3io/wp/backup/adapters/__init__.py

@@ -0,0 +1,9 @@
+"""Real implementations of the ports: subprocess, filesystem, tar, crypto.
+
+May import ``domain/``, ``ports/`` and ``core/`` (AD-1). An adapter *holds* a
+core object and satisfies a Protocol; it never subclasses the core.
+"""
+
+from __future__ import annotations
+
+__all__: list[str] = []

l3io/wp/backup/adapters/clock.py

@@ -0,0 +1,22 @@
+"""The real ``ports.clock.Clock``."""
+
+from __future__ import annotations
+
+import time
+from datetime import UTC, datetime
+
+__all__ = ["SystemClock"]
+
+
+class SystemClock:
+    """The system wall clock, in UTC."""
+
+    __slots__ = ()
+
+    def now(self) -> datetime:
+        """``datetime.now(UTC)``."""
+        return datetime.now(UTC)
+
+    def monotonic_ns(self) -> int:
+        """``time.monotonic_ns()``."""
+        return time.monotonic_ns()