Repository navigation
v0.14.1 Release #3434
Description
I think with the multiple recent breakages we've just had due to dependency upgrades, we should push out a patch release with some haste.
Please comment/add/object
Must have
- numpy 1.18 support test failure with upstream-dev #3409
- pseudonetcdf 3.1.0 support test failure with upstream-dev #3409, Restore crashing CI tests on pseudonetcdf-3.1 #3420
- require cftime != 1.0.4 unpin cftime #3463
- groupby reduce regression fix Another groupby.reduce bugfix. #3403
- pandas master support Build failure with pandas master #3440
Nice to have
- ellipsis (...) work Transpose some but not all dimensions #1081, Allow ellipsis in place of xr.ALL_DIMS? #3414, change ALL_DIMS to equal ellipsis #3418, Allow ellipsis (...) in transpose #3421, add
ALL_DIMSinxr.dot#3423, enable xr.ALL_DIMS in xr.dot #3424 - HTML repr Html repr #3425 (really mouth-watering, but I'm unsure about how far it is from completion)
- groupby drop nan groups Drop groups associated with nans in group variable #3406
- deprecate
allow_lazyDeprecate allow_lazy #3435 - __dask_tokenize__ __dask_tokenize__ #3446
- dask name equality Optimize dask array equality checks. #3453
- Leave empty slot when not using accessors Leave empty slot when not using accessors #3531
Activity
dcherian commentedon Oct 22, 2019
#3406 needs a review
mathause commentedon Oct 28, 2019
Would be nice to get this out - just hit #3426. (I now updated to master but this is besides the point).
crusaderky commentedon Oct 29, 2019
@mathause I'm personally really uncomfortable pushing out a release when there are multiple known breakages against dependencies - see Must have list. Help is welcome!
crusaderky commentedon Oct 29, 2019
@barronh any update re pseudonetcdf 3.1?
barronh commentedon Oct 31, 2019
I believe there are two issues here.
First, the 3.1 release was not 2.7 compliant. It mixed named keyword arguments with
**kwds. That could be fixed easily.Second, the camx reader changed subclasses, which affects the xarray test for CF variables. I could update the test that would fix xarray test-case.
crusaderky commentedon Oct 31, 2019
@barronh, we don't care about Python 2.7 compliance. We support >=3.6.
barronh commentedon Nov 4, 2019
Got it. This is a test update to a test that is backward and forward compatible. I'll get something checked in.
mathause commentedon Nov 5, 2019
xref for numpy 1.18 numpy/numpy#14831
dcherian commentedon Nov 5, 2019
@mathause Thanks for filing these upstream issues!
dcherian commentedon Nov 7, 2019
Once #3491 is merged, we should be ready to release since numpy will fix itself (numpy/numpy#14841)
mathause commentedon Nov 7, 2019
Don't we have to figure out whether to use
np.meanornp.nanmeanfor datetime vectors?dcherian commentedon Nov 11, 2019
I'm in favour of releasing even if we are currently broken with numpy master.
Our current release is also broken with numpy master, so the situation is no worse...
crusaderky commentedon Nov 15, 2019
If someone could review and merge #3537 and #3531, we can close this!
crusaderky commentedon Nov 19, 2019
I think we're good to go!
dcherian commentedon Nov 19, 2019
I agree! @crusaderky, @max-sixty: do either of you have the time to make a release?
max-sixty commentedon Nov 19, 2019
Yup I can do it later this afternoon!
dcherian commentedon Nov 19, 2019
👍
dcherian commentedon Nov 19, 2019
Thanks @max-sixty I activated the RTD build.