-
Notifications
You must be signed in to change notification settings - Fork 2
Draft
Conversation
@soapy1
soapy1
changed the title
(削除) User requested specs (削除ここまで)
(追記) Determine user requested specs (追記ここまで)
Feb 18, 2025
@soapy1
soapy1
force-pushed
the
user-requested-specs
branch
2 times, most recently
from
February 18, 2025 23:55
dd0bd89 to
86de305
Compare
@soapy1
soapy1
force-pushed
the
user-requested-specs
branch
from
February 20, 2025 00:49
86de305 to
229290a
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.
Uh oh!
There was an error while loading. Please reload this page.
This PR proposes a way for understanding the user requested specs in an environment. This will be different for a conda env and pixi env. This pr focuses on conda env first.
It uses conda's history class for getting the user requested specs from the environment. When the dof checkpoint is created, the user requested specs are marked and will include the conda-build/rattler compatible string representation of the MatchSpec.
Try it out
what about pip
The goal is to be able to fully recreate something like conda's environment.yaml. In order to do this, dof must also understand what pip packages the user has installed.
Currently, dof is able to inspect an environment and see pip installed packages. I don't expect this has enough information to make a confident guess at which packages are specifically requested by a user or not. More investigation is needed for this.
next steps