You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Every tool's install and uninstall steps are Python #208
Install steps run once on a fresh machine, which is the hardest time to find out they are broken. 9 tools have an install.bash, not counting the drafts in wip/ folders that #127 reviews, and 12 have an uninstall.bash, and features/install/tools.bash and features/install/utils.bash run and support them.
Ideal state
Every tool's install and uninstall steps, and the scripts in features/install/ that run them, are Python, tested by tests that import them
Installing or uninstalling a tool does what it did before
How does a fresh Mac get uv and Python before the first script needs them? (new process or runtime) Open in how-does-a-fresh-mac-get-uv-and-python-before-the-first-script-needs-them.md. Setup runs install steps on a fresh Mac, so they move to Python only once this is answered. Uninstall steps do not wait for it.
Starting points
features/install/tools.bash: runs the install steps
tools/macos/install.bash: an install step with a one-time side effect
tools/neovim/uninstall.bash: an uninstall step
Depends on
The sub-issue that sets up the repo-level Python project: the ported code needs the project to live in
Activity