-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
0.16.0 release #4031
Comments
|
As discussed on the dev call, I'll take this one. I think we need to do 0.16.0 as we had some backward-incompat changes (I can't remember now what they were; but can hunt them down if anyone otherwise has a preference for 0.15.2?) |
Agree! I'll keep an eye on those this week. |
👍 I'm also not sure what the bug is. In fact it's possible that a bug was fixed and a workaround is what's raising the error now :P Re: #3891 do you mean set |
Exactly, so this will push to 0.17 |
FYI I will do this towards the end of this week or at the latest this weekend |
Thanks @max-sixty ! |
It'd be nice to issue a release soon. We should decide if this is a minor 0.15.2 or major 0.16.0
Please edit this list as you wish.
Must-have
Support multiple dimensions in DataArray.argmin() and DataArray.argmax() methods #3936 multiple dims argmin, argmax
Sparse DataArray indexing gives incorrect results #4019, Fix conversion of multiindexed pandas objects to sparse xarray objects #4088; MultiIndex to sparse DataArray bug
FIX: correct dask array handling in _calc_idxminmax #3922 fix dask array handling in idxmax, idxmin
Incoherencies between docs in open_mfdataset and combine_by_coords and its behaviour. #4009, Fix 4009 #4173 combine_attrs with open_mfdataset
Transpose coords by default #3824 transpose coords (if major release)
Remove old auto combine #3926 remove old autocombine
Correct dask handling for 1D idxmax/min on ND data #4135 nD dask arrays in idxmax/min
Nice to have
The text was updated successfully, but these errors were encountered: