Repository navigation
Conversation
Contributor
|
Could you work off of the feature/pixi branch instead and see if that works with your setup? I would like to modernize the installation tools, and that branch is fully moved into the pyproject.toml with both conda-forge and pypi dependencies specified. The idea is the pixi.lock file should supplant the environment.yml files if you want fixed dependencies. |
This branch has not been deployed
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
2 participants
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.
Pydap just had a 3.5.11 release that removed some modules.
Pydap was imported in mod_maker and used to grab MERRA2 data when we were considering which met product to use.
This limits pydap to <3.5.11 to avoid the ModuleNotFoundError that would result from a pip install of ginput.
But eventually we may want to trim the legacy code off mod_maker and drop the pydap import.