uv-stack 0.8.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- uv_stack-0.8.1/.gitignore +77 -0
- uv_stack-0.8.1/CHANGELOG.md +346 -0
- uv_stack-0.8.1/PKG-INFO +1204 -0
- uv_stack-0.8.1/README.md +1185 -0
- uv_stack-0.8.1/pyproject.toml +76 -0
- uv_stack-0.8.1/src/uv_stack/__init__.py +3 -0
- uv_stack-0.8.1/src/uv_stack/cli/__init__.py +389 -0
- uv_stack-0.8.1/src/uv_stack/cli/_complete.py +110 -0
- uv_stack-0.8.1/src/uv_stack/cli/_render.py +166 -0
- uv_stack-0.8.1/src/uv_stack/cli/completion_cmd.py +29 -0
- uv_stack-0.8.1/src/uv_stack/cli/config_cmd.py +158 -0
- uv_stack-0.8.1/src/uv_stack/cli/create.py +323 -0
- uv_stack-0.8.1/src/uv_stack/cli/delete.py +156 -0
- uv_stack-0.8.1/src/uv_stack/cli/diff_cmd.py +194 -0
- uv_stack-0.8.1/src/uv_stack/cli/doctor.py +110 -0
- uv_stack-0.8.1/src/uv_stack/cli/edit.py +292 -0
- uv_stack-0.8.1/src/uv_stack/cli/init_cmd.py +95 -0
- uv_stack-0.8.1/src/uv_stack/cli/list_cmd.py +169 -0
- uv_stack-0.8.1/src/uv_stack/cli/refresh_cmd.py +91 -0
- uv_stack-0.8.1/src/uv_stack/cli/resolve.py +67 -0
- uv_stack-0.8.1/src/uv_stack/cli/show.py +215 -0
- uv_stack-0.8.1/src/uv_stack/cli/status_cmd.py +80 -0
- uv_stack-0.8.1/src/uv_stack/cli/sync_cmd.py +336 -0
- uv_stack-0.8.1/src/uv_stack/cli/transfer_cmd.py +207 -0
- uv_stack-0.8.1/src/uv_stack/cli/upgrade.py +300 -0
- uv_stack-0.8.1/src/uv_stack/commands.py +218 -0
- uv_stack-0.8.1/src/uv_stack/config.py +674 -0
- uv_stack-0.8.1/src/uv_stack/editor.py +178 -0
- uv_stack-0.8.1/src/uv_stack/errors.py +92 -0
- uv_stack-0.8.1/src/uv_stack/fsutil.py +996 -0
- uv_stack-0.8.1/src/uv_stack/hints.py +75 -0
- uv_stack-0.8.1/src/uv_stack/models.py +170 -0
- uv_stack-0.8.1/src/uv_stack/operations/__init__.py +0 -0
- uv_stack-0.8.1/src/uv_stack/operations/create.py +96 -0
- uv_stack-0.8.1/src/uv_stack/operations/delete.py +452 -0
- uv_stack-0.8.1/src/uv_stack/operations/diff.py +529 -0
- uv_stack-0.8.1/src/uv_stack/operations/doctor.py +1639 -0
- uv_stack-0.8.1/src/uv_stack/operations/edit.py +237 -0
- uv_stack-0.8.1/src/uv_stack/operations/export.py +391 -0
- uv_stack-0.8.1/src/uv_stack/operations/importing.py +1261 -0
- uv_stack-0.8.1/src/uv_stack/operations/init.py +47 -0
- uv_stack-0.8.1/src/uv_stack/operations/portable.py +681 -0
- uv_stack-0.8.1/src/uv_stack/operations/project.py +932 -0
- uv_stack-0.8.1/src/uv_stack/operations/pyproject.py +461 -0
- uv_stack-0.8.1/src/uv_stack/operations/remote.py +520 -0
- uv_stack-0.8.1/src/uv_stack/operations/scaffold.py +586 -0
- uv_stack-0.8.1/src/uv_stack/operations/status.py +188 -0
- uv_stack-0.8.1/src/uv_stack/operations/upgrade.py +516 -0
- uv_stack-0.8.1/src/uv_stack/parse.py +226 -0
- uv_stack-0.8.1/src/uv_stack/pyversion.py +148 -0
- uv_stack-0.8.1/src/uv_stack/render.py +162 -0
- uv_stack-0.8.1/src/uv_stack/resolver.py +308 -0
- uv_stack-0.8.1/src/uv_stack/runner.py +425 -0
- uv_stack-0.8.1/src/uv_stack/variables.py +555 -0
- uv_stack-0.8.1/tasks.py +68 -0
- uv_stack-0.8.1/tests/__init__.py +0 -0
- uv_stack-0.8.1/tests/conftest.py +187 -0
- uv_stack-0.8.1/tests/test_cli.py +6869 -0
- uv_stack-0.8.1/tests/test_commands.py +189 -0
- uv_stack-0.8.1/tests/test_config.py +769 -0
- uv_stack-0.8.1/tests/test_delete_cli.py +298 -0
- uv_stack-0.8.1/tests/test_delete_op.py +560 -0
- uv_stack-0.8.1/tests/test_diff.py +896 -0
- uv_stack-0.8.1/tests/test_doctor.py +2968 -0
- uv_stack-0.8.1/tests/test_edit.py +809 -0
- uv_stack-0.8.1/tests/test_encoding.py +157 -0
- uv_stack-0.8.1/tests/test_errors.py +28 -0
- uv_stack-0.8.1/tests/test_export.py +367 -0
- uv_stack-0.8.1/tests/test_fsutil.py +2125 -0
- uv_stack-0.8.1/tests/test_hints.py +79 -0
- uv_stack-0.8.1/tests/test_importing.py +1535 -0
- uv_stack-0.8.1/tests/test_init_op.py +62 -0
- uv_stack-0.8.1/tests/test_models.py +103 -0
- uv_stack-0.8.1/tests/test_operations.py +4776 -0
- uv_stack-0.8.1/tests/test_parse.py +153 -0
- uv_stack-0.8.1/tests/test_portable.py +1279 -0
- uv_stack-0.8.1/tests/test_pyproject_ops.py +775 -0
- uv_stack-0.8.1/tests/test_pyversion.py +167 -0
- uv_stack-0.8.1/tests/test_remote.py +1014 -0
- uv_stack-0.8.1/tests/test_render.py +205 -0
- uv_stack-0.8.1/tests/test_resolver.py +262 -0
- uv_stack-0.8.1/tests/test_runner.py +578 -0
- uv_stack-0.8.1/tests/test_scaffold.py +1143 -0
- uv_stack-0.8.1/tests/test_status_op.py +356 -0
- uv_stack-0.8.1/tests/test_transfer_cli.py +619 -0
- uv_stack-0.8.1/tests/test_variables.py +603 -0
- uv_stack-0.8.1/uv.lock +965 -0
- uv_stack-0.8.1/vrzn.toml +19 -0
|
@@ -0,0 +1,77 @@
|
|
|
1
|
+
# Created by .gitignore support plugin (hsz.mobi)
|
|
2
|
+
.idea
|
|
3
|
+
.vscode
|
|
4
|
+
*.sublime-*
|
|
5
|
+
|
|
6
|
+
### Python template
|
|
7
|
+
# Byte-compiled / optimized / DLL files
|
|
8
|
+
__pycache__/
|
|
9
|
+
*.py[cod]
|
|
10
|
+
|
|
11
|
+
# C extensions
|
|
12
|
+
*.so
|
|
13
|
+
|
|
14
|
+
# Distribution / packaging
|
|
15
|
+
.Python
|
|
16
|
+
.venv/
|
|
17
|
+
venv/
|
|
18
|
+
env/
|
|
19
|
+
build/
|
|
20
|
+
develop-eggs/
|
|
21
|
+
dist/
|
|
22
|
+
eggs/
|
|
23
|
+
lib/
|
|
24
|
+
lib64/
|
|
25
|
+
parts/
|
|
26
|
+
sdist/
|
|
27
|
+
var/
|
|
28
|
+
*.egg-info/
|
|
29
|
+
.installed.cfg
|
|
30
|
+
*.egg
|
|
31
|
+
|
|
32
|
+
# PyInstaller
|
|
33
|
+
# Usually these files are written by a python script from a template
|
|
34
|
+
# before PyInstaller builds the exe, so as to inject date/other infos into it.
|
|
35
|
+
*.manifest
|
|
36
|
+
*.spec
|
|
37
|
+
|
|
38
|
+
# Installer logs
|
|
39
|
+
pip-log.txt
|
|
40
|
+
pip-delete-this-directory.txt
|
|
41
|
+
|
|
42
|
+
# Unit test / coverage reports
|
|
43
|
+
htmlcov/
|
|
44
|
+
.tox/
|
|
45
|
+
.coverage
|
|
46
|
+
.cache
|
|
47
|
+
nosetests.xml
|
|
48
|
+
coverage.xml
|
|
49
|
+
|
|
50
|
+
# Translations
|
|
51
|
+
*.mo
|
|
52
|
+
*.pot
|
|
53
|
+
|
|
54
|
+
# Django stuff:
|
|
55
|
+
*.log
|
|
56
|
+
|
|
57
|
+
# Sphinx documentation
|
|
58
|
+
docs/_build/
|
|
59
|
+
|
|
60
|
+
# PyBuilder
|
|
61
|
+
target/
|
|
62
|
+
|
|
63
|
+
# Mac Stuff
|
|
64
|
+
.DS_Store
|
|
65
|
+
|
|
66
|
+
# Claude stuff
|
|
67
|
+
.claude
|
|
68
|
+
docs/plans
|
|
69
|
+
docs/specs
|
|
70
|
+
docs/superpowers
|
|
71
|
+
docs/hyperpowers
|
|
72
|
+
|
|
73
|
+
# Project tooling + planning artifacts
|
|
74
|
+
.superpowers
|
|
75
|
+
.mypy_cache
|
|
76
|
+
.pytest_cache
|
|
77
|
+
.ruff_cache
|
|
@@ -0,0 +1,346 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
Notable changes to uv-stack are documented in this file, beginning with 0.6.0.
|
|
4
|
+
Earlier releases predate it.
|
|
5
|
+
|
|
6
|
+
The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) with
|
|
7
|
+
one addition, a `Breaking` section for changes that alter existing behavior, and
|
|
8
|
+
this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
9
|
+
|
|
10
|
+
## 0.8.1 - 2026-11-18
|
|
11
|
+
|
|
12
|
+
### Fixed
|
|
13
|
+
|
|
14
|
+
- `stack doctor` reported every environment that had been built as an
|
|
15
|
+
"Env-like directory with no stack.txt" error, telling you to create a
|
|
16
|
+
`stack.txt` that was already there. The check counted the `requirements.in`
|
|
17
|
+
and `environment.yml` a build writes as signs of an env, but never looked
|
|
18
|
+
for `stack.txt` itself. It now reports only a directory that has those files
|
|
19
|
+
and no `stack.txt`. The false error dates from 0.6.0.
|
|
20
|
+
|
|
21
|
+
## 0.8.0 - 2026-10-05
|
|
22
|
+
|
|
23
|
+
### Added
|
|
24
|
+
|
|
25
|
+
- `stack delete`, the inverse of `stack create`: `delete profile NAME` and
|
|
26
|
+
`delete bundle NAME` remove the YAML, `delete env NAME` removes the
|
|
27
|
+
micromamba environment and then `envs/NAME/`, and `delete project` withdraws
|
|
28
|
+
uv-stack from the project in the current directory, running `uv remove` for
|
|
29
|
+
the packages it applied and dropping the `[tool.uv-stack]` table while
|
|
30
|
+
leaving `pyproject.toml`, `uv.lock`, `.venv/` and your own dependencies in
|
|
31
|
+
place. Each form asks before it acts (`-y` answers yes). A profile or
|
|
32
|
+
bundle is refused while an environment's `stack.txt` or another bundle
|
|
33
|
+
still refers to it, naming each place, since a bare token would silently
|
|
34
|
+
start meaning the pip package of that name; `--force` deletes anyway and
|
|
35
|
+
warns per reference. Only an environment with a `stack.txt` under the
|
|
36
|
+
config root can be deleted, so a micromamba environment uv-stack does not
|
|
37
|
+
manage is never removed.
|
|
38
|
+
- A setting written more than once in one host's entry of `remotes.yaml` is
|
|
39
|
+
warned about, naming its lines and the one that is used, since YAML keeps
|
|
40
|
+
only the last. `stack config remote list`, `set` and `remove`,
|
|
41
|
+
`stack sync remote` and `stack edit remotes` print the warning on stderr, and
|
|
42
|
+
`stack doctor` reports it. `set` and `remove` keep the used value when they
|
|
43
|
+
rewrite the file. A merge key (`<<`) is not counted. Before, the earlier
|
|
44
|
+
values were silently ignored.
|
|
45
|
+
|
|
46
|
+
### Fixed
|
|
47
|
+
|
|
48
|
+
- Commands that write under the config root refuse one reached through a
|
|
49
|
+
symbolic link to a directory that does not exist, such as a
|
|
50
|
+
`~/.config/python-envs` linked to a checkout or mount that is not there yet.
|
|
51
|
+
The refusal names the link and its target, and says how to restore or create
|
|
52
|
+
it. That covers `stack create profile`, `bundle`, `env` and `project`, the
|
|
53
|
+
`stack delete` forms, `stack refresh`, `stack config remote set` and
|
|
54
|
+
`remove`, `stack config portable`, and `stack edit` for everything but
|
|
55
|
+
`project`.
|
|
56
|
+
Before, `stack create profile`, `bundle` and `env` and
|
|
57
|
+
`stack config remote set` created the missing directory and wrote into it,
|
|
58
|
+
leaving a near-empty tree where the checkout belonged, and
|
|
59
|
+
`stack config portable` failed with "File exists". A file at
|
|
60
|
+
or above the root is refused as "Not a directory", naming it.
|
|
61
|
+
- `stack config init` creates the missing target of such a link and says so,
|
|
62
|
+
and `stack init` offers to create it, with `--yes` accepting. `stack doctor`
|
|
63
|
+
reports the link and its missing target with both ways out, and
|
|
64
|
+
`doctor --fix` leaves that choice to you. Before, `stack config init` and
|
|
65
|
+
`stack init` failed with "File exists", and `stack doctor` reported the root
|
|
66
|
+
as missing with a fix that failed the same way.
|
|
67
|
+
|
|
68
|
+
## 0.7.2 - 2026-09-30
|
|
69
|
+
|
|
70
|
+
### Fixed
|
|
71
|
+
|
|
72
|
+
- `stack import` takes its locks, reads the target, writes the files, and
|
|
73
|
+
builds the environments in one tree when the config root is reached through
|
|
74
|
+
a symbolic link. Before, a link retargeted while an import ran could leave
|
|
75
|
+
the locks held in one tree while the import read, wrote, and built in
|
|
76
|
+
another, where nothing serialized it with a concurrent import or writer. Its
|
|
77
|
+
warnings and refusals still name the root as given; an error panel from a
|
|
78
|
+
build may name the tree the link resolved to.
|
|
79
|
+
- `stack import --dry-run` refuses a config root with a file or a broken
|
|
80
|
+
symbolic link above it, such as a `~/.config` linked to a checkout that is
|
|
81
|
+
not there, as the import itself does. Before, the dry run planned an import
|
|
82
|
+
the real run refused.
|
|
83
|
+
|
|
84
|
+
## 0.7.1 - 2026-09-30
|
|
85
|
+
|
|
86
|
+
### Fixed
|
|
87
|
+
|
|
88
|
+
- `stack import` prints a newline or tab in an environment name as its escape
|
|
89
|
+
where it names the environments that use a changed file, and in its warning
|
|
90
|
+
that an environment could not be read. Its output keeps newlines and tabs
|
|
91
|
+
for the conflict diff's layout, so a directory under `envs/` whose name held
|
|
92
|
+
one could print a line of its choosing.
|
|
93
|
+
- Tables and plain output print a control character as its escape, keeping
|
|
94
|
+
newlines and tabs, as error panels and warnings already did. That covers
|
|
95
|
+
`stack list`, `stack show`, `stack status`, `stack diff` and the other plain
|
|
96
|
+
lines, plus `stack doctor --fix` outcomes and the rules and summary of
|
|
97
|
+
`stack upgrade` and `stack sync`. Before, an escape sequence in a profile or
|
|
98
|
+
bundle description or tag, which `stack import` installs from another
|
|
99
|
+
machine, or in a directory name under `envs/`, reached the terminal, which
|
|
100
|
+
acts on it. The note under `stack status`, those upgrade and sync lines,
|
|
101
|
+
and `doctor --fix` outcomes spell a newline too, since each names an
|
|
102
|
+
environment listed from disk on a single line it could otherwise break.
|
|
103
|
+
- `stack import` no longer refuses a shipped file that is a hard link, or a
|
|
104
|
+
symbolic link, on this machine. The write replaces that name alone, so the
|
|
105
|
+
file's other names keep their content. Before, it was refused as "the same
|
|
106
|
+
file" as another definition file, with a hint about directory links. Shipping
|
|
107
|
+
the file a symbolic link points at is still refused, since the link would
|
|
108
|
+
read the new content, and the refusal now says the other file is a symbolic
|
|
109
|
+
link. An environment that uses a hard link to a shipped profile or bundle is
|
|
110
|
+
no longer listed as one of its users.
|
|
111
|
+
- `stack create profile`, `stack create bundle`, `stack create env` (including
|
|
112
|
+
`--python` with `--recreate`), `stack init`, and the legacy-profile
|
|
113
|
+
conversion in `stack doctor --fix` take their lock, check for conflicts, and
|
|
114
|
+
write in one tree when the config root is reached through a symbolic link.
|
|
115
|
+
Before, a link retargeted while one of them ran could leave the lock held in
|
|
116
|
+
one tree while the checks and the file went to another, where nothing
|
|
117
|
+
serialized them with a concurrent writer.
|
|
118
|
+
|
|
119
|
+
## 0.7.0 - 2026-09-30
|
|
120
|
+
|
|
121
|
+
### Added
|
|
122
|
+
|
|
123
|
+
- `stack export [ITEMS...]` writes the named environments, profiles, and
|
|
124
|
+
bundles, everything they reach, and each environment's lock as one JSON
|
|
125
|
+
document on standard output or to `-o FILE`.
|
|
126
|
+
- `stack import FILE|-` installs the definitions from an export document,
|
|
127
|
+
reporting new/identical/replace/remove outcomes for each file. A file that
|
|
128
|
+
differs from this machine's copy is refused with a diff and the environments
|
|
129
|
+
that use it, unless `--overwrite` is given. `--dry-run` reports changes
|
|
130
|
+
without writing. `--strict` refuses unqualified stack names. A meaning change
|
|
131
|
+
(importing a profile when an environment's stack names it as a package) is
|
|
132
|
+
refused even with `--overwrite`. Missing variables are appended to
|
|
133
|
+
`variables.txt`. After writing, each imported environment is built (created,
|
|
134
|
+
synced, or recreated per environment) with the shipped pins as preferences,
|
|
135
|
+
and a pin report shows how many pins were kept, changed, dropped, or added.
|
|
136
|
+
`--no-build` installs definitions without building. `--recreate` wipes and
|
|
137
|
+
rebuilds each environment from the shipped pins (plain dotted Python only).
|
|
138
|
+
- Unless `--no-build` is given, `stack import` refuses before writing anything
|
|
139
|
+
when an imported environment references a variable with no value on this
|
|
140
|
+
machine, installs an editable checkout that is missing, already runs a
|
|
141
|
+
Python outside its plain `python.txt` version without `--recreate`, or has a
|
|
142
|
+
`python.txt` that is not a plain version with `--recreate`.
|
|
143
|
+
- `stack import` names the environments it did not rebuild that use a replaced
|
|
144
|
+
profile or bundle, and also those that reach an unchanged bundle whose bare
|
|
145
|
+
token a newly imported profile now captures.
|
|
146
|
+
- On a target that folds letter case, `stack import` reports the environments
|
|
147
|
+
that use a definition a shipped case variant replaces (`profiles/Foo.yaml`
|
|
148
|
+
over `profiles/foo.yaml`), in both the conflict report and the not-rebuilt
|
|
149
|
+
line.
|
|
150
|
+
- `stack sync remote [ITEMS...] DEST` exports the named items (or the whole
|
|
151
|
+
root) and imports them on a remote machine over ssh, running `ssh DEST <stack>
|
|
152
|
+
import -` with the document on stdin. The local exit status is the remote's.
|
|
153
|
+
`--remote-stack` and `--remote-root` customize the remote command and root.
|
|
154
|
+
- `remotes.yaml` maps host names to optional `stack` and `root` settings,
|
|
155
|
+
overridden by `--remote-stack` and `--remote-root`. Portable across machines.
|
|
156
|
+
A host listed twice is refused, since YAML would keep only the last entry.
|
|
157
|
+
`stack doctor` reports an invalid file.
|
|
158
|
+
- `stack edit remotes` opens `remotes.yaml` in the editor and validates it when
|
|
159
|
+
the editor exits, offering the editor again when it does not validate, as for
|
|
160
|
+
the other kinds.
|
|
161
|
+
- `stack config remote list|set|remove` lists, sets, and removes `remotes.yaml`
|
|
162
|
+
entries. `set` and `remove` take a lock on the config root, keep a symlinked
|
|
163
|
+
file's link and the file's permission bits, and refuse a file that holds
|
|
164
|
+
comments, since the rewrite normalizes formatting and would drop them.
|
|
165
|
+
|
|
166
|
+
### Changed
|
|
167
|
+
|
|
168
|
+
- `stack doctor`'s missing-checkout finding looks up a relative editable path
|
|
169
|
+
from the directory doctor runs in, where uv resolves it, instead of from the
|
|
170
|
+
config root. This changes an existing finding: the same root can now report
|
|
171
|
+
a checkout missing from one directory and present from another.
|
|
172
|
+
`stack import` checks editables the same way.
|
|
173
|
+
- `stack doctor`'s missing-checkout finding also checks an editable given as a
|
|
174
|
+
local `file:` URL (`-e file:///src/pkg`), which it previously skipped as a
|
|
175
|
+
remote install. `stack import`'s pre-flight checks it the same way.
|
|
176
|
+
- A name holding a control character, such as an escape or a NUL, or a name
|
|
177
|
+
that is not valid UTF-8 is now refused wherever a NAME is taken, as a name
|
|
178
|
+
holding whitespace already was. `stack export` refuses such a name on disk
|
|
179
|
+
rather than ship a document that every `stack import` would refuse.
|
|
180
|
+
- Error panels, warnings, `stack doctor` findings and `stack status` messages
|
|
181
|
+
print a control character in their text as its escape (for example `\x1b`),
|
|
182
|
+
keeping newlines and tabs, so a name or value read from disk cannot drive
|
|
183
|
+
the terminal. `stack import` prints everything it reports the same way, the
|
|
184
|
+
conflict diff included.
|
|
185
|
+
|
|
186
|
+
## 0.6.0 - 2026-09-28
|
|
187
|
+
|
|
188
|
+
### Breaking
|
|
189
|
+
|
|
190
|
+
- `stack show env|profile|bundle NAME` and `stack status NAMES...` now apply
|
|
191
|
+
the same file-stem rule the create and edit commands apply, so a NAME holding
|
|
192
|
+
a path separator, a `.` or `..` segment, `:`, `@`, whitespace, or a leading
|
|
193
|
+
`-` is refused instead of being joined onto the config root and read. A
|
|
194
|
+
hand-made directory carrying such a name is still listed by `stack list env`
|
|
195
|
+
and by a bare `stack status`; naming it on the command line is what stopped
|
|
196
|
+
working, and renaming the directory on disk is what makes it nameable again.
|
|
197
|
+
- `stack upgrade --no-upgrade` and `stack upgrade --upgrade-package PKG` now
|
|
198
|
+
preserve the pins the published lock already holds. Both previously compiled
|
|
199
|
+
into an empty file, and `uv pip compile` reads prior pins out of its output
|
|
200
|
+
file, so either flag silently re-resolved every distribution.
|
|
201
|
+
- A config file that is a directory, a dangling symlink, or a FIFO is now a
|
|
202
|
+
ConfigError instead of reading as absent. This covers `project-python.txt`,
|
|
203
|
+
`editor.txt`, and an environment's `python.txt`, `micromamba.txt`, and
|
|
204
|
+
`channels.txt`, each of which previously fell back to its default. For all but
|
|
205
|
+
`python.txt` that happened while `stack doctor` reported the root clean; a
|
|
206
|
+
non-regular `python.txt` was reported, but as missing (see Fixed).
|
|
207
|
+
- `[tool.uv-stack].python` refuses an empty or space-padded value. An empty
|
|
208
|
+
value previously read as "no preference" and fell through to the machine
|
|
209
|
+
default; a padded one defeated the version test and was taken to name a
|
|
210
|
+
micromamba environment.
|
|
211
|
+
- A requirement entry that spans more than one line or ends in a trailing
|
|
212
|
+
backslash is refused. Both shapes were previously written and rendered into
|
|
213
|
+
`requirements.in` verbatim, where a continuation swallows the requirement
|
|
214
|
+
written after it. `stack create env|profile|bundle`, `stack init`, and
|
|
215
|
+
`stack edit` refuse one on the way in; because rendering validates too, every
|
|
216
|
+
command that renders — `upgrade`, `sync`, `status`, `show env`, `refresh`,
|
|
217
|
+
`create project` — now also refuses one already sitting in a `stack.txt` or a
|
|
218
|
+
profile.
|
|
219
|
+
|
|
220
|
+
### Added
|
|
221
|
+
|
|
222
|
+
- `stack sync` creates, builds, and recompiles every environment the config
|
|
223
|
+
root declares, without a prompt and creating missing environments rather
|
|
224
|
+
than reporting them as errors, which makes it the first command to run on a
|
|
225
|
+
freshly cloned config root. `stack sync env NAME...` does the same for only
|
|
226
|
+
the named environments. Both accept `--dry-run`, `--stop-on-error`,
|
|
227
|
+
`--strict`, and `--upgrade`.
|
|
228
|
+
- `stack sync project TOKENS...` adds tokens to the tracked project in the
|
|
229
|
+
current directory and re-resolves it. The tokens are appended to the stack
|
|
230
|
+
the project already records, never replacing it, so an existing token is not
|
|
231
|
+
lost by forgetting to repeat it. The run goes through the same interrupted-run
|
|
232
|
+
recovery as `stack refresh` and accepts the same `--python`, `--strict`,
|
|
233
|
+
`--no-sync`, and `--dry-run` flags.
|
|
234
|
+
- `stack diff SOURCE SOURCE` compares two environments across the four layers
|
|
235
|
+
uv-stack records: the interpreter, the micromamba packages, the effective
|
|
236
|
+
channel order, and the compiled pins. A source is an environment in this
|
|
237
|
+
config root, a copy of another machine's `envs/<name>/` directory, or a bare
|
|
238
|
+
`requirements.lock.txt`, which carries pins only and is reported as such
|
|
239
|
+
rather than as matching. It exits 0 on a difference unless given
|
|
240
|
+
`--exit-code`, and `--json` emits the comparison for scripts.
|
|
241
|
+
- Config roots can declare variables in `variables.txt`, supply this machine's
|
|
242
|
+
values in `variables.local.txt` or in an exported environment variable of the
|
|
243
|
+
same name, and reference them as `${NAME}` in profiles, bundles, and
|
|
244
|
+
`stack.txt`. References are expanded when generating `requirements.in` and
|
|
245
|
+
when calling `uv add`, but a tracked project's ledger keeps the unexpanded
|
|
246
|
+
entry so the project travels.
|
|
247
|
+
- `stack config portable` writes a managed `.gitignore` block so a config root
|
|
248
|
+
can be committed and cloned. It never invokes git itself: it prints the
|
|
249
|
+
commands for you to run, and `--dry-run` prints the plan without writing.
|
|
250
|
+
- `stack create project` and `stack refresh` warn when the interpreter spec they
|
|
251
|
+
record will not resolve on another machine — either an absolute path, or a
|
|
252
|
+
micromamba environment that exists only here.
|
|
253
|
+
- `stack doctor` gained diagnostics for sources it cannot read or parse,
|
|
254
|
+
missing editable checkouts, unsafe variable expansion, and a portable
|
|
255
|
+
`.gitignore` block that is absent or stale.
|
|
256
|
+
- `stack doctor` warns when a name is published as both a profile and a
|
|
257
|
+
bundle. Resolution is unchanged and still documented -- bare reaches the
|
|
258
|
+
profile, `@<name>` the bundle -- but the only report of the collision used
|
|
259
|
+
to come from the resolver, on the runs that happened to reference the name.
|
|
260
|
+
It is a warning rather than an error, and `--fix` does not touch it: both
|
|
261
|
+
files are valid, and choosing which to withdraw is not doctor's to make.
|
|
262
|
+
|
|
263
|
+
### Changed
|
|
264
|
+
|
|
265
|
+
- `stack show env` prints a note and exits 0 when `requirements.in` cannot be
|
|
266
|
+
rendered, matching what `stack status` already did. It previously printed the
|
|
267
|
+
whole description and then exited 1, while `--json` exited 0 on the same
|
|
268
|
+
root.
|
|
269
|
+
- The upgrade and sync batch summary reports three outcomes rather than
|
|
270
|
+
two: succeeded, failed, and skipped. A `--dry-run` batch prints the summary
|
|
271
|
+
too, where it previously printed none and still exited 1 when an environment
|
|
272
|
+
failed.
|
|
273
|
+
- The package declares POSIX support in its classifiers. `fcntl`, `pty`,
|
|
274
|
+
`termios`, `O_NOFOLLOW`, and `O_NONBLOCK` are all absent on Windows, where
|
|
275
|
+
`stack config portable` can create an absent ignore file but cannot refresh
|
|
276
|
+
an existing one.
|
|
277
|
+
|
|
278
|
+
### Fixed
|
|
279
|
+
|
|
280
|
+
- `stack upgrade` publishes `requirements.lock.txt` with the mode every other
|
|
281
|
+
generated file gets rather than `mkstemp`'s 0600, which on a config root
|
|
282
|
+
shared with a second account left the lock the one generated file they could
|
|
283
|
+
not read.
|
|
284
|
+
- `stack upgrade NAME NAME` upgrades that environment once instead of twice.
|
|
285
|
+
- A filesystem error in one environment no longer aborts the whole batch; it is
|
|
286
|
+
reported in the summary like any other failure.
|
|
287
|
+
- An environment that `--stop-on-error` abandoned after an earlier failure is
|
|
288
|
+
reported as skipped rather than as a success.
|
|
289
|
+
- `stack doctor` no longer answers for a path it could not read. An unsearchable
|
|
290
|
+
config root previously turned `profiles/`, `bundles/`, and `envs/` into
|
|
291
|
+
"missing" errors offering a `mkdir` that would fail for the same reason the
|
|
292
|
+
stat did, and a top-level directory it could not enumerate produced no finding
|
|
293
|
+
at all.
|
|
294
|
+
- `stack doctor` no longer calls a `python.txt` that is present but not a
|
|
295
|
+
regular file missing, a report whose offered repair could not run because the
|
|
296
|
+
entry was already there.
|
|
297
|
+
- `stack doctor` reports an environment whose `stack.txt` is not a regular file.
|
|
298
|
+
Such an environment is dropped from every listing in the program, and doctor
|
|
299
|
+
skipped it on the same probe and printed "No problems detected."
|
|
300
|
+
- `stack doctor` reports an env-like directory under `envs/` that has no
|
|
301
|
+
`stack.txt` at all -- one holding a `requirements.in` or an `environment.yml`,
|
|
302
|
+
so a sync ran there. It is dropped from every listing for the same reason,
|
|
303
|
+
which left a bare `stack sync` passing over it without a word -- or, with no
|
|
304
|
+
other environment declared, answering that there were none -- while its own
|
|
305
|
+
compiled lock sat beside it. A directory under `envs/` with no
|
|
306
|
+
such marker is still not reported: it is not a broken environment, it is not
|
|
307
|
+
an environment.
|
|
308
|
+
- An unreadable `bundles/` no longer fails a command that resolved a bare
|
|
309
|
+
profile token. The shadow warning -- the one saying a name matches both a
|
|
310
|
+
profile and a bundle -- probed `bundles/<name>.yaml` to decide whether to
|
|
311
|
+
print, and that probe raises rather than answering no when the directory
|
|
312
|
+
cannot be searched, so `stack status`, `stack show env`, and `stack upgrade`
|
|
313
|
+
exited 1 over a directory none of them needed to read. The warning is now
|
|
314
|
+
skipped when the probe cannot answer; the resolution it decorated is
|
|
315
|
+
unchanged, and `stack doctor` still reports the directory.
|
|
316
|
+
- Every YAML loader failure on a profile or bundle becomes a ConfigError. Only
|
|
317
|
+
`YAMLError` was converted before, so a document whose constructor raises
|
|
318
|
+
something else -- a date of `2020-99-99`, or `!!bool "nope"` -- came out of
|
|
319
|
+
`stack doctor` as a traceback.
|
|
320
|
+
- `stack create project` resuming an interrupted run keeps editable, VCS, and
|
|
321
|
+
path entries in `tracking.applied` instead of deleting them, which silently
|
|
322
|
+
handed ownership of those dependencies back to the user.
|
|
323
|
+
- An environment marker no longer hides a requirement's name from ownership
|
|
324
|
+
tracking. A `/` or `\` anywhere in the entry, including inside the marker,
|
|
325
|
+
made it read as a path and so as user-owned.
|
|
326
|
+
- Runs that rewrite a tracked project's `[tool.uv-stack]` table -- `stack
|
|
327
|
+
refresh`, `stack sync project`, and `stack create project` -- take a
|
|
328
|
+
per-project lock, so a second run in the same project waits up to five
|
|
329
|
+
seconds and is then refused. Unserialized, the last run to write the table
|
|
330
|
+
replaced it with the view it had read at the start, so two `stack sync
|
|
331
|
+
project` runs could each drop the other's token. `--dry-run` does not wait.
|
|
332
|
+
Where the config root cannot lock, `stack doctor` says so and these runs stay
|
|
333
|
+
unserialized.
|
|
334
|
+
|
|
335
|
+
### Security
|
|
336
|
+
|
|
337
|
+
- `stack upgrade` validates every NAME before it starts the batch, so a name
|
|
338
|
+
that would escape the config root is refused rather than used to read another
|
|
339
|
+
directory's sources and overwrite its generated files.
|
|
340
|
+
- The guarded read behind `stack config portable` — a command new in this
|
|
341
|
+
release, so no published version was exposed — refuses an existing
|
|
342
|
+
`.gitignore` that is a symlink or that carries a second hard link, and
|
|
343
|
+
refuses outright on a platform without `O_NOFOLLOW` and `O_NONBLOCK` rather
|
|
344
|
+
than degrading to an unguarded open. A refresh preserves everything outside
|
|
345
|
+
the managed block byte for byte, so each route would otherwise copy a planted
|
|
346
|
+
file's contents into the `.gitignore` you go on to commit.
|