Repository navigation
Wingbox 0.7.0: native Windows support
Wingbox runs natively on Windows (issue #48). The test suite runs on Linux,
macOS and Windows with Python 3.11, 3.12 and 3.13 in GitHub Actions.
Changes
- Windows support: the build, queries, the hooks,
wingbox install,
wingbox updateand the background refresh of the graph work on Windows.
Locks, detached processes, atomic file replacement and worker processes go
through one module of platform differences (scripts/portable.py). - The worker processes of the build start with
spawnwhereforkdoes not
exist; the graph is byte for byte the same whatever the start method. - On Windows,
wingbox installwrites the Claude Code hooks in exec form (the
full path ofwingbox.exeand its arguments apart), which Claude Code starts
without Git Bash or PowerShell. - The plugin's Claude Code hooks are in exec form too (
shwith the launcher
and its arguments as a list), as the Claude Code documentation advises for a
path under${CLAUDE_PLUGIN_ROOT}; on macOS and Linux they run as before. - With no
EDITORorVISUALset,wingbox learnoffers Notepad on Windows. - README: PowerShell forms of the Docker and script examples, and how to use
Wingbox on Windows without Git for Windows.
Fixes
- Every path Wingbox stores in
.wingbox/, prints or compares is written with
/on every system; paths from a person or a hook (backslashes, a Git Bash
drive such as/c/Users/..., the\\?\prefix, another drive) are
normalised where they come in. - Every file Wingbox writes uses UTF-8 and LF line endings; source files with
CRLF line endings give the same graph, line numbers included. - Output is written as UTF-8 whatever the console code page, and colours are
used only on a terminal that shows them (NO_COLORis respected). gitoutput is read as UTF-8, with file names unquoted.- No
SyntaxWarningon the first run under Python 3.13; a test compiles every
source file with warnings turned into errors.