pyselfupdate 0.3.2__tar.gz → 0.4.0__tar.gz

{pyselfupdate-0.3.2 → pyselfupdate-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: pyselfupdate
-Version: 0.3.2
+Version: 0.4.0
 Summary: Self-update and update notification for Python CLIs installed with uv tool
 Keywords: uv,cli,self-update,update-notifier,release
 Author: Chris Birch
@@ -18,7 +18,7 @@ Requires-Dist: typer>=0.12.0 ; extra == 'typer'
 Requires-Python: >=3.11
 Project-URL: Repository, https://github.com/datapointchris/pyselfupdate
 Project-URL: Issues, https://github.com/datapointchris/pyselfupdate/issues
-Project-URL: Changelog, https://github.com/datapointchris/pyselfupdate/blob/main/CHANGELOG.md
+Project-URL: Changelog, https://github.com/datapointchris/pyselfupdate/releases
 Provides-Extra: typer
 Description-Content-Type: text/markdown
 
@@ -218,7 +218,8 @@ command, and nothing above the `Source` protocol learns either name.
 
 ## State
 
-`${XDG_STATE_HOME:-~/.local/state}/<tool>/autoupdate.json`, written atomically:
+`${XDG_STATE_HOME:-~/.local/state}/<tool>/autoupdate-<machine>.json`, written
+atomically:
 
 ```json
 {
@@ -237,6 +238,13 @@ the user, and deleting it changes behaviour rather than merely costing a
 recompute. That is `XDG_STATE_HOME` by the Base Directory specification, and it
 is where `gh` puts the same thing.
 
+`<machine>` is the bare lowercased hostname, from `state.machine()`. It is in
+the name because both fields that vary — the version installed here, and the
+instant this box last checked — describe one machine. A state directory shared
+between machines, by a file syncer or a network home directory, otherwise has
+two writers on one path and reports whichever wrote last as the state of all of
+them.
+
 The timestamp is written **before** the network call. `gh` stamps only on
 success, so a rate-limited or offline user re-hits the API on every invocation
 until the window resets; an interval exists to bound the request rate, and only
@@ -244,11 +252,10 @@ this ordering actually does that.
 
 ## Siblings
 
-The same two-layer design in other languages. **`update` exists in all three;
-the `notify` layer, the shared `autoupdate.json` schema and the
-`NO_AUTO_UPDATE` contract are implemented in this library and in its bash
-sibling, and are still to be added to goselfupdate** — until then goselfupdate
-provides the update half only.
+The same two-layer design in other languages. All three carry both layers, and
+they share the `autoupdate-<machine>.json` schema, the machine derivation that
+names it, and the `NO_AUTO_UPDATE` contract. They do not share an API, because
+"update" means a different operation in each.
 
 - [goselfupdate](https://github.com/datapointchris/goselfupdate) — replaces a Go binary
 - [bashselfupdate](https://github.com/datapointchris/bashselfupdate) — moves a git checkout to its newest tag

{pyselfupdate-0.3.2 → pyselfupdate-0.4.0}/README.md

@@ -194,7 +194,8 @@ command, and nothing above the `Source` protocol learns either name.
 
 ## State
 
-`${XDG_STATE_HOME:-~/.local/state}/<tool>/autoupdate.json`, written atomically:
+`${XDG_STATE_HOME:-~/.local/state}/<tool>/autoupdate-<machine>.json`, written
+atomically:
 
 ```json
 {
@@ -213,6 +214,13 @@ the user, and deleting it changes behaviour rather than merely costing a
 recompute. That is `XDG_STATE_HOME` by the Base Directory specification, and it
 is where `gh` puts the same thing.
 
+`<machine>` is the bare lowercased hostname, from `state.machine()`. It is in
+the name because both fields that vary — the version installed here, and the
+instant this box last checked — describe one machine. A state directory shared
+between machines, by a file syncer or a network home directory, otherwise has
+two writers on one path and reports whichever wrote last as the state of all of
+them.
+
 The timestamp is written **before** the network call. `gh` stamps only on
 success, so a rate-limited or offline user re-hits the API on every invocation
 until the window resets; an interval exists to bound the request rate, and only
@@ -220,11 +228,10 @@ this ordering actually does that.
 
 ## Siblings
 
-The same two-layer design in other languages. **`update` exists in all three;
-the `notify` layer, the shared `autoupdate.json` schema and the
-`NO_AUTO_UPDATE` contract are implemented in this library and in its bash
-sibling, and are still to be added to goselfupdate** — until then goselfupdate
-provides the update half only.
+The same two-layer design in other languages. All three carry both layers, and
+they share the `autoupdate-<machine>.json` schema, the machine derivation that
+names it, and the `NO_AUTO_UPDATE` contract. They do not share an API, because
+"update" means a different operation in each.
 
 - [goselfupdate](https://github.com/datapointchris/goselfupdate) — replaces a Go binary
 - [bashselfupdate](https://github.com/datapointchris/bashselfupdate) — moves a git checkout to its newest tag

{pyselfupdate-0.3.2 → pyselfupdate-0.4.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "pyselfupdate"
-version = "0.3.2"
+version = "0.4.0"
 description = "Self-update and update notification for Python CLIs installed with uv tool"
 readme = "README.md"
 keywords = [
@@ -36,7 +36,7 @@ typer = ["typer>=0.12.0"]
 [project.urls]
 Repository = "https://github.com/datapointchris/pyselfupdate"
 Issues = "https://github.com/datapointchris/pyselfupdate/issues"
-Changelog = "https://github.com/datapointchris/pyselfupdate/blob/main/CHANGELOG.md"
+Changelog = "https://github.com/datapointchris/pyselfupdate/releases"
 
 [dependency-groups]
 dev = [

{pyselfupdate-0.3.2 → pyselfupdate-0.4.0}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "pyselfupdate"
-version = "0.3.2"
+version = "0.4.0"
 description = "Self-update and update notification for Python CLIs installed with uv tool"
 authors = [{ name = "Chris Birch", email = "datapointchris@gmail.com" }]
 license = { text = "MIT" }
@@ -34,7 +34,7 @@ typer = ["typer>=0.12.0"]
 [project.urls]
 Repository = "https://github.com/datapointchris/pyselfupdate"
 Issues = "https://github.com/datapointchris/pyselfupdate/issues"
-Changelog = "https://github.com/datapointchris/pyselfupdate/blob/main/CHANGELOG.md"
+Changelog = "https://github.com/datapointchris/pyselfupdate/releases"
 
 [dependency-groups]
 dev = [

{pyselfupdate-0.3.2 → pyselfupdate-0.4.0}/src/pyselfupdate/state.py

@@ -1,8 +1,8 @@
-"""The per-tool state file.
+"""The per-tool, per-machine state file.
 
 One schema, shared byte-for-byte with goselfupdate and bashselfupdate, so that
 any tool can read any other tool's state and a single dashboard can glob
-`~/.local/state/*/autoupdate.json` with no per-tool knowledge.
+`~/.local/state/*/autoupdate-*.json` with no per-tool knowledge.
 
 State, not config and not cache: it persists across runs, it is not authored by
 the user, and deleting it changes behaviour rather than merely costing a
@@ -14,6 +14,7 @@ from __future__ import annotations
 
 import json
 import os
+import socket
 from dataclasses import asdict
 from dataclasses import dataclass
 from datetime import UTC
@@ -21,7 +22,45 @@ from datetime import datetime
 from pathlib import Path
 
 SCHEMA = 1
-FILENAME = 'autoupdate.json'
+
+#: Names the file when the host cannot be read, so a filename is always
+#: well-formed and two unidentifiable boxes collide only with each other.
+UNKNOWN_MACHINE = 'unknown'
+
+
+def machine() -> str:
+    """The box this process runs on: bare hostname, no domain, lowercased.
+
+    goselfupdate and bashselfupdate derive it the same way, so the three write
+    interleaved files a single reader can enumerate.
+    """
+    try:
+        return canonical_machine(socket.gethostname())
+    except OSError:
+        return UNKNOWN_MACHINE
+
+
+def canonical_machine(name: str) -> str:
+    """A hostname from any source, reduced to the form `machine` records.
+
+    A hostname reaches a reader fully qualified as often as bare, so a
+    comparison against a recorded name has to canonicalize both sides or it
+    fails on every host.
+    """
+    return name.strip().lower().split('.')[0] or UNKNOWN_MACHINE
+
+
+def filename(machine_name: str) -> str:
+    """The file one machine writes inside a tool's state directory.
+
+    The machine is part of the name because a state directory is a synced
+    directory on some installations, and a file syncer has no merge: two boxes
+    writing one path leaves one winner plus a conflict copy nobody reads. Both
+    fields this file carries — the version installed here and the instant this
+    box last checked — describe one machine, so the split costs nothing and
+    makes the collision unreachable.
+    """
+    return f'autoupdate-{machine_name}.json'
 
 
 @dataclass
@@ -54,7 +93,8 @@ def state_home() -> Path:
 
 
 def state_path(tool: str) -> Path:
-    return state_home() / tool / FILENAME
+    """Where this machine's state for a tool lives."""
+    return state_home() / tool / filename(machine())
 
 
 def read(tool: str) -> State: