runspec-linux 0.4.2__tar.gz → 0.4.3__tar.gz

{runspec_linux-0.4.2 → runspec_linux-0.4.3}/CHANGELOG.md

@@ -1,5 +1,14 @@
 # runspec-linux Changelog
 
+## [0.4.3] — 2026-06-21
+
+- **`install-into-venv --venv` and `configure-pip --venv` are now marked
+  `ui = "directory"`.** Both point at an existing venv *folder*, so the console's
+  path picker opens a folder picker ("Use this folder") instead of a file picker
+  — it was previously unclear the arg wanted the venv directory, not the
+  `bin/python` inside it. (`install-into-venv --project` stays a generic `path`
+  since it accepts either a project directory or a wheel/sdist file.)
+
 ## [0.4.2] — 2026-06-21
 
 Add 3 runnables for managing Python virtualenvs on a fleet host — thin wrappers

{runspec_linux-0.4.2 → runspec_linux-0.4.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: runspec-linux
-Version: 0.4.2
+Version: 0.4.3
 Summary: Linux system admin runnables for runspec
 Requires-Python: >=3.10
 Requires-Dist: runspec-linux-core>=0.3.2

{runspec_linux-0.4.2 → runspec_linux-0.4.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "runspec-linux"
-version = "0.4.2"
+version = "0.4.3"
 requires-python = ">=3.10"
 description = "Linux system admin runnables for runspec"
 dependencies = [

{runspec_linux-0.4.2 → runspec_linux-0.4.3}/runspec_linux/runspec.toml

@@ -508,6 +508,7 @@ output      = "json"
 
 [install-into-venv.args.venv]
 type        = "path"
+ui          = "directory"
 short       = "-v"
 description = "Path to the venv to install into (its bundled python runs pip)"
 
@@ -611,6 +612,7 @@ description = "Where to write pip.conf: user (~/.config/pip/pip.conf) or venv (<
 
 [configure-pip.args.venv]
 type        = "path"
+ui          = "directory"
 description = "Venv path for --scope venv (the file is written to <venv>/pip.conf)"
 required    = false