fix: install via venv on Linux#4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary: avoid system pip and PEP 668 failures in macOS/Linux install/update flows by using repo-local .venv; update Codex and Claude Code skills to prefer the venv CLI; remove POSIX uninstall pip dependency; add backup-root fallback when ~/Documents is unusable; add compatibility tests for missing pip, PEP 668 avoidance, temp HOME/Documents behavior, and skill link conflicts. Validation: python -m unittest discover -s tests; python -m compileall src scripts; quick_validate for both skills; venv editable install smoke with CLI doctor; git diff --check.