Closed regro-cf-autotick-bot closed 2 years ago
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:
Documentation on acceptable licenses can be found here.
@conda-forge-admin please restart ci
@WeatherGod there are many dependencies broken in the stack up to here and they don't seem to be supported upstream anymore. This probably won't work unless we find new champions for these packages.
Ugh. I have been using pynio for reading grib2 model data for a few years now (through xarray). While not perfect, it is the only stable grib2 reader that can be used with xarray that I know of (yes, I am familiar with cfgrib, but last I checked, it wasn't stable -- maybe that changed?).
Maybe I can take a peek at some of the dependencies and see if I can get them unstuck a bit.
Probably easier to "freeze" an old environment with a working version than fixing this. BTW, cfgrib got better, I would check it out again.
Freezing the environment is tricky because of the numpy and netcdf4 dependencies, and the current working build isn't all that great, either. My workplace is already experiencing issues doing a conda create
off of a simple package list that includes pynio (something is causing a bad build of another package to get included). I keep having to pass around my working environment's conda list --export
to get them unstuck. I don't know how long that is going to be viable.
I am glad to see cfgrib is getting better. My bigger criteria is API stability. That was the nice thing about pynio. It was extremely stable.
I keep having to pass around my working environment's
conda list --export
to get them unstuck. I don't know how long that is going to be viable.
I recommend conda-lock for that: https://github.com/conda-incubator/conda-lock
I am glad to see cfgrib is getting better. My bigger criteria is API stability. That was the nice thing about pynio. It was extremely stable.
I understand but looks like upstream discontinued it in lieu for other packages (cfgrib?).
I see that this PR has conflicts, and I'm the only committer. I'm going to close this PR and will make another one as appropriate. This was generated by https://github.com/regro/autotick-bot/actions/runs/2056137957
This PR has been triggered in an effort to update python39.
Notes and instructions for merging this PR:
Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.
This package has the following downstream children:
And potentially more.
If this PR was opened in error or needs to be updated please add the
bot-rerun
label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have theconda-forge-admin
add it for you.This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (
conda install -c conda-forge rever
) and pip (pip install re-ver
) installable. Finally, feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/357375166, please use this URL for debugging