-
Notifications
You must be signed in to change notification settings - Fork 2
different behavior in pixi v conda env #44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@e-marshall can you post the output of your I wish conda had better native support of lock files! If it is a version issue that can be fixed by changing the pins, currently it's a manual step to re-generate conda files from the locked pixi environment: |
yeah, this is definitely my bad @scottyhq , i mixed up an older env i'd been using when i first combined the books with the env file from the instructions 😢. Name Version Build Channel |
ran the book in fresh repos/envs testing conda and pixi and works fine so going to close this |
Trying in a fresh pixi env there's some slight changes in behavior from when i run in an env created with mamba/conda-forge. haven't looked into it yet but first guess is its due to pkg versions (prob xarray)?
running list of differences here then will try to pin down cause
pixi env has xr 2025.1.2, conda has xr 2024.10.0
np.unique(single_glacier_raster.satellite_img1)
,single_glacier_raster = single_glacier_raster.compute()
, get the following warning:Seems related to this
The text was updated successfully, but these errors were encountered: