Closed ehogan closed 5 days ago
ine second - I just want to see if the pin impacts support for Python 3.12, brb
I am not terribly keen on introducing such a pin. We could do it for the v2.11.0 release, but should remove it again asap as this kind of pinning has given us a lot of work in the past.
I am not terribly keen on introducing such a pin. We could do it for the v2.11.0 release, but should remove it again asap as this kind of pinning has given us a lot of work in the past.
ha, I was posting the same while you were too - great :brain: think alike :laughing:
do you know anyone who knows R and would be willing to minimally maintain those recipes?
No
I am not terribly keen on introducing such a pin. We could do it for the v2.11.0 release, but should remove it again asap as this kind of pinning has given us a lot of work in the past.
Yes, I agree, it's not ideal. However, once the ncdf4 package (which is the package I believe is causing the problems for the recipe_combined_indices.yml
and recipe_extreme_events.yml
recipes) has been upgraded to work with R>=4.3.0, the pin would no longer be needed ๐
Alternatively, we don't pin, I have a go at fixing fix the miles
recipes, and we add the other two to the list of broken recipes?
OK merging this now, but we need to remove the pin as soon as it will be possible :+1:
Description
Closes #3674
Link to documentation:
Before you get started
Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the ๐ Technical or ๐งช Scientific review.
To help with the number of pull requests: