chore(nix): improve nix setup to be locally editable #1219
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
with these simple changes, the default nix environment has editable local files, so there's no need to reload any time a package is changed when using it.
Pull Request Test Coverage Report for Build 17799166997Details
💛 - Coveralls |
grdsdev
approved these changes
Sep 17, 2025
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.
What kind of change does this PR introduce?
Make the python packages in the nix dev environment locally editable.
What is the current behavior?
Currently, the nix setup copies all the python packages to the nix store, which makes them immutable. When locally making changes, it is necessary to reload the environment whenever a change is made, which is not ergonomic.
What is the new behavior?
We can make it editable by leveraging the
mkEditablePythonOverlayfunction fromuv2nix, which lets you decide on a workspace root to read the packages from. This is done through the$REPO_ROOTenv var, set by the default environment'sshellHook, which should always point to the repository root.