Create editable SDK workspaces with shared activation - #4028
Closed
TomCC7 wants to merge 1 commit into
Closed
Conversation
TomCC7
added this pull request to stack #4031
September 9, 2026 19:59
❌ 8 Tests Failed:
View the full list of 8 ❄️ flaky test(s)
To view more test analytics, go to the Test Analytics Dashboard |
TomCC7
force-pushed
the
feat/installer-environments
branch
from
September 9, 2026 23:59
2d43b9e to
d57ec24
Compare
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
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.
Superseded by the replacement Python dimup stack: #4042 → #4043 → #4044 → #4045 → #4046 → #4047. See the onboarding PRD for the current review map.
Turns the installation core into a one-shot SDK workspace creator. It generates an editable Python package with an external hello blueprint, a test, lockfiles, and optional direnv configuration. Developers own the generated source and pyproject; --restore preserves edits and uses the existing locks. --contributor prepares a DimOS checkout.
There is no persistent second CLI or Pixi task interface. Users source one activation script and then use dimos, Python, pytest, and uv. The shared Bash/Zsh/direnv activation applies Pixi plus uv and supplies a complete manual deactivate operation without installing anything during activation.
Validation: this layer passes 8 Rust tests and standalone Clippy. Bash/Zsh tests cover quoting, repeated activation, and restoration of the original exported environment. The final stack also tests direnv in CI.