Repository navigation
Developer Bootstrap Stack: Stacks for Spack development - #6970
Open
johnwparent wants to merge 3 commits into
Open
johnwparent wants to merge 3 commits into
johnwparent wants to merge 3 commits into
Conversation
johnwparent
requested review from
alalazo,
eugeneswalker,
kwryankrattiger,
trws and
zackgalbreath
as code owners
October 8, 2026 22:25
johnwparent
force-pushed
the
update-ruff-ty-bc
branch
from
October 9, 2026 16:45
ae5dff6 to
205c0eb
Compare
johnwparent
force-pushed
the
update-ruff-ty-bc
branch
2 times, most recently
from
October 19, 2026 21:36
5ac8511 to
3861d79
Compare
Factors out packages in the generic dev tools stack that were speficially there for Spack development into their own stacks Allows generic dev tools stack to move versions of those packages forward independent of Spack's needs Allows for more specificity in the Spack developer tools stack without limiting the general purpose dev tools stack Signed-off-by: John Parent <john.parent@kitware.com>
Signed-off-by: John Parent <john.parent@kitware.com>
johnwparent
force-pushed
the
update-ruff-ty-bc
branch
from
October 20, 2026 15:27
ad34edd to
a3c1291
Compare
Signed-off-by: John Parent <john.parent@kitware.com>
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.
Pulls the "spack development requirements" out of the generic general purpose dev tools stack, and into their own, targeted stack.
This allows use to configure and constrain the specs we need to bootstrap Spack's dev dependencies independent of the larger environment they were being concretized in, and in turn allows the dev tools stack to build the latest of these tools, which is more in line with the intent of that stack.
Pulls
ruff,tyandpytestout into their own stack, and builds ty and ruff with two different pythons, 3.10 for compatibility with older systems and latest stable.Rust is factored out into its own group so the various ruff and tys can share a rust.
The biggest win here is this gives us a clear place to manage the packages that will form the base of the eventual "spack developer environment" and allows us to configure that stack as Spack developer needs change without needing to worry about a much larger stack.
This stack is also built in a way that is intended to be compatible with the upcoming common-stack work.