Alternative CondaMultiPlatformEnvironmentExporter
#15240
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
…nvironmentExporter
…nvironmentExporter
3 tasks
CodSpeed Instrumentation Performance ReportMerging #15240 will not alter performanceComparing Summary
|
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.
Description
Alternative to #15142
The code is identical with the exception of abstracting the environment extrapolation logic away from
conda.cli.main_export. Instead each CondaEnvironmentExporter implements a__call__that standardizes erroring (if multiple platforms are requested for a single platform exporter) or extrapolating (for each platform requested).Closes #15159 (the issue)
Closes #15142 (the original PR)
Checklist - did you ...
newsdirectory (using the template) for the next release's release notes?