uv-launch 0.2.2__tar.gz → 0.2.3__tar.gz

uv_launch-0.2.2/README.md → uv_launch-0.2.3/PKG-INFO

@@ -1,3 +1,13 @@
+Metadata-Version: 2.3
+Name: uv-launch
+Version: 0.2.3
+Summary: Immediate Python command startup with atomic background updates through uv
+Requires-Dist: packaging>=24
+Requires-Dist: platformdirs>=4.8
+Requires-Python: >=3.11
+Project-URL: Repository, https://github.com/nimashoghi/uv-launch
+Description-Content-Type: text/markdown
+
 # uv-launch
 
 Install Python commands that start immediately and update in the background. The foreground shell shim executes an already installed environment. It does not invoke uv or wait for network access.
@@ -13,7 +23,9 @@ uv-launch update my-command
 uv-launch status my-command
 ```
 
-`--bin-dir` defaults to `~/.local/bin`. Use a separate directory for evaluation. The installer refuses to overwrite commands it does not own. `UV_LAUNCH_HOME` selects the installation-state directory; its default is `~/.local/share/uv-launch`.
+Directory defaults come from [platformdirs](https://platformdirs.readthedocs.io/en/latest/api.html): `user_bin_path()` for installed commands and `user_data_path("uv-launch", appauthor=False)` for durable installations. On macOS the data directory is `~/Library/Application Support/uv-launch`; on Linux it follows `XDG_DATA_HOME`, normally `~/.local/share/uv-launch`. Both platforms normally install commands in `~/.local/bin`. `--bin-dir` and a nonempty `UV_LAUNCH_HOME` override those defaults. Use a separate directory for evaluation. The installer refuses to overwrite commands it does not own.
+
+To adopt the platform directory after upgrading from 0.2.2 or earlier, repeat the original `install` or `install-source` command with its existing requirements and options, without a `UV_LAUNCH_HOME` override. This builds and validates a new installation before replacing its launcher. Keep the old directory while any process uses it; do not move its virtual environments, whose executable paths are absolute. Existing launchers retain their recorded directory until reinstalled. To operate on an old installation directly, set `UV_LAUNCH_HOME` to its recorded root.
 
 Each invocation captures the current immutable generation and starts a detached update check. Concurrent checks for the same tool coalesce under a process lock. A check resolves all requested packages together, pinning Git dependencies to concrete revisions. If the resolved installation is unchanged, it keeps the existing environment. Otherwise it creates a new environment at its final path, checks dependencies and loads the Python entrypoint (or verifies ownership of a wheel-provided executable), then atomically switches the generation used by future launches. Virtual environments are never moved after creation, because their scripts contain absolute paths.
 
@@ -77,7 +89,7 @@ uv-launch install codexr \
   --with 'codex-monitor @ git+https://github.com/nimashoghi/codex-router.git@main#subdirectory=packages/codex-monitor' \
   --with 'codex-recovery @ git+https://github.com/nimashoghi/codex-router.git@main#subdirectory=packages/codex-recovery' \
   --with 'codex-accounts @ git+https://github.com/nimashoghi/codex-router.git@main#subdirectory=packages/codex-accounts' \
-  --bin-dir ~/.local/share/codexr-evaluation/bin
+  --bin-dir ./codexr-evaluation/bin
 ```
 
 Use that isolated command before choosing to replace an existing launcher. Updating the local codexr suite and preparing that exact suite on an SSH host remain separate responsibilities; uv-launch contains no Codex or SSH runtime logic.

uv_launch-0.2.2/PKG-INFO → uv_launch-0.2.3/README.md

@@ -1,12 +1,3 @@
-Metadata-Version: 2.3
-Name: uv-launch
-Version: 0.2.2
-Summary: Immediate Python command startup with atomic background updates through uv
-Requires-Dist: packaging>=24
-Requires-Python: >=3.11
-Project-URL: Repository, https://github.com/nimashoghi/uv-launch
-Description-Content-Type: text/markdown
-
 # uv-launch
 
 Install Python commands that start immediately and update in the background. The foreground shell shim executes an already installed environment. It does not invoke uv or wait for network access.
@@ -22,7 +13,9 @@ uv-launch update my-command
 uv-launch status my-command
 ```
 
-`--bin-dir` defaults to `~/.local/bin`. Use a separate directory for evaluation. The installer refuses to overwrite commands it does not own. `UV_LAUNCH_HOME` selects the installation-state directory; its default is `~/.local/share/uv-launch`.
+Directory defaults come from [platformdirs](https://platformdirs.readthedocs.io/en/latest/api.html): `user_bin_path()` for installed commands and `user_data_path("uv-launch", appauthor=False)` for durable installations. On macOS the data directory is `~/Library/Application Support/uv-launch`; on Linux it follows `XDG_DATA_HOME`, normally `~/.local/share/uv-launch`. Both platforms normally install commands in `~/.local/bin`. `--bin-dir` and a nonempty `UV_LAUNCH_HOME` override those defaults. Use a separate directory for evaluation. The installer refuses to overwrite commands it does not own.
+
+To adopt the platform directory after upgrading from 0.2.2 or earlier, repeat the original `install` or `install-source` command with its existing requirements and options, without a `UV_LAUNCH_HOME` override. This builds and validates a new installation before replacing its launcher. Keep the old directory while any process uses it; do not move its virtual environments, whose executable paths are absolute. Existing launchers retain their recorded directory until reinstalled. To operate on an old installation directly, set `UV_LAUNCH_HOME` to its recorded root.
 
 Each invocation captures the current immutable generation and starts a detached update check. Concurrent checks for the same tool coalesce under a process lock. A check resolves all requested packages together, pinning Git dependencies to concrete revisions. If the resolved installation is unchanged, it keeps the existing environment. Otherwise it creates a new environment at its final path, checks dependencies and loads the Python entrypoint (or verifies ownership of a wheel-provided executable), then atomically switches the generation used by future launches. Virtual environments are never moved after creation, because their scripts contain absolute paths.
 
@@ -86,7 +79,7 @@ uv-launch install codexr \
   --with 'codex-monitor @ git+https://github.com/nimashoghi/codex-router.git@main#subdirectory=packages/codex-monitor' \
   --with 'codex-recovery @ git+https://github.com/nimashoghi/codex-router.git@main#subdirectory=packages/codex-recovery' \
   --with 'codex-accounts @ git+https://github.com/nimashoghi/codex-router.git@main#subdirectory=packages/codex-accounts' \
-  --bin-dir ~/.local/share/codexr-evaluation/bin
+  --bin-dir ./codexr-evaluation/bin
 ```
 
 Use that isolated command before choosing to replace an existing launcher. Updating the local codexr suite and preparing that exact suite on an SSH host remain separate responsibilities; uv-launch contains no Codex or SSH runtime logic.

{uv_launch-0.2.2 → uv_launch-0.2.3}/pyproject.toml

@@ -1,10 +1,13 @@
 [project]
 name = "uv-launch"
-version = "0.2.2"
+version = "0.2.3"
 description = "Immediate Python command startup with atomic background updates through uv"
 readme = "README.md"
 requires-python = ">=3.11"
-dependencies = ["packaging>=24"]
+dependencies = [
+    "packaging>=24",
+    "platformdirs>=4.8",
+]
 
 [project.urls]
 Repository = "https://github.com/nimashoghi/uv-launch"

{uv_launch-0.2.2 → uv_launch-0.2.3}/pyproject.toml.orig

@@ -1,10 +1,10 @@
 [project]
 name = "uv-launch"
-version = "0.2.2"
+version = "0.2.3"
 description = "Immediate Python command startup with atomic background updates through uv"
 readme = "README.md"
 requires-python = ">=3.11"
-dependencies = ["packaging>=24"]
+dependencies = ["packaging>=24", "platformdirs>=4.8"]
 
 [project.urls]
 Repository = "https://github.com/nimashoghi/uv-launch"

{uv_launch-0.2.2 → uv_launch-0.2.3}/src/uv_launch/__init__.py

@@ -21,6 +21,8 @@ from contextlib import contextmanager
 from dataclasses import asdict, dataclass
 from pathlib import Path
 
+from platformdirs import user_bin_path, user_data_path
+
 LOGGER = logging.getLogger(__name__)
 
 
@@ -53,7 +55,9 @@ def _run_checked(arguments: list[str], **kwargs) -> None:
 
 def state_root() -> Path:
     """Return durable installation state, independently of any current project."""
-    return Path(os.environ.get("UV_LAUNCH_HOME", "~/.local/share/uv-launch")).expanduser().resolve()
+    if override := os.environ.get("UV_LAUNCH_HOME"):
+        return Path(override).expanduser().resolve()
+    return user_data_path("uv-launch", appauthor=False).resolve()
 
 
 def tool_directory(name: str) -> Path:
@@ -376,7 +380,7 @@ def main(argv: list[str] | None = None) -> int:
         "--entrypoint", help="installed console script, defaults to command name"
     )
     installing.add_argument("--python", default="3.13", help="uv Python interpreter selector")
-    installing.add_argument("--bin-dir", default="~/.local/bin")
+    installing.add_argument("--bin-dir", default=user_bin_path())
     installing.add_argument(
         "--timeout", type=float, default=600, help="seconds per update operation"
     )
@@ -389,7 +393,7 @@ def main(argv: list[str] | None = None) -> int:
     source_installing.add_argument("--revision", default="main", help="branch, tag, or commit")
     source_installing.add_argument("--with", dest="extra", action="append", default=[])
     source_installing.add_argument("--python", default="3.13")
-    source_installing.add_argument("--bin-dir", default="~/.local/bin")
+    source_installing.add_argument("--bin-dir", default=user_bin_path())
     source_installing.add_argument("--timeout", type=float, default=600)
     source_installing.add_argument(
         "--prepare",