Skip to content

build: remove the dead bsander uv source override - #181

Merged
jcschaff merged 1 commit into
mainfrom
deps/remove-bsander-override
Sep 23, 2026
Merged

jcschaff merged 1 commit into
mainfrom
deps/remove-bsander-override

Conversation

@jcschaff

Copy link
Copy Markdown
Contributor

Removes [tool.uv.sources] bsander = { git = … } from pyproject.toml. This closes one of the three open follow-ups from PRs #168/#169, recorded as F14 in docs/plan-testing.md.

Why it was dead. bsander is in no dependency list and has no lock entry, and it returns 404 on PyPI. A uv.sources entry only redirects a package that something actually depends on, so this one did nothing. uv lock is unchanged by the removal, which confirms it.

Why remove it anyway. If anyone ever added bsander to dependencies, the override would silently start applying. Local and container builds would then pull an unpinned git main, while a built wheel would still declare a package that PyPI cannot supply.

bsander itself is to be archived under strategy decision 1, phase 1.

make check clean. F14 in docs/plan-testing.md is updated to record the removal; the client-side installability check it also calls for remains open.

🤖 Generated with Claude Code

bsander appears in no dependency list and no lock entry and is not on
PyPI, so the override was inert; uv lock is unchanged by removing it.
Deleting it keeps it from becoming load-bearing if bsander is ever added
as a dependency (F14 in docs/plan-testing.md).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@jcschaff
jcschaff merged commit 06d6d6e into main Sep 23, 2026
6 checks passed
@jcschaff
jcschaff deleted the deps/remove-bsander-override branch September 23, 2026 12:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant