Skip to content
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

bump min deps for 0.15 #3713

Merged
merged 13 commits into from
Jan 24, 2020
Merged

bump min deps for 0.15 #3713

merged 13 commits into from
Jan 24, 2020

Conversation

dcherian
Copy link
Contributor

@dcherian dcherian commented Jan 21, 2020

@dcherian dcherian mentioned this pull request Jan 21, 2020
11 tasks
ci/requirements/doc.yml Outdated Show resolved Hide resolved
@@ -40,7 +40,7 @@ dependencies:
- pytest-cov
- pytest-env
- rasterio=1.0
- scipy=1.0 # Policy allows for 1.2, but scipy>=1.1 breaks numpy=1.14
- scipy=1.2 # Policy allows for 1.3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not use 1.3 then?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was getting segmentation faults locally. I'll bump once I fix the tests.

- scipy 1.3
- bottleneck 1.3
- h5py 2.10
- rasterio 1.1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

py36-min-all-deps.yml should have matching changes for bottleneck, h5py, rasterio

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I'm doing this incrementally since the env wasn't getting created locally.

- bottleneck 1.3
- h5py 2.10
- rasterio 1.1
- pseudonetcdf
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about pseudonetcdf?

xarray/core/dataset.py Outdated Show resolved Hide resolved
xarray/core/nputils.py Outdated Show resolved Hide resolved
@jthielen
Copy link
Contributor

looks like pint doesn't have nanquantile?

@dcherian Hope you don't mind me jumping in, but that is correct at the moment (see hgrecco/pint#981). It would be easy to add to Pint, though.

@keewis
Copy link
Collaborator

keewis commented Jan 21, 2020

as @jthielen said, it does not since I never realized we used nanquantile (did we change that recently?). For now, I'd mark these tests as xfail(reason="not implemented by pint") since none of the pint-support PRs are merged yet. Can be a new PR, though.

@pep8speaks
Copy link

pep8speaks commented Jan 21, 2020

Hello @dcherian! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2020-01-24 17:47:42 UTC

@dcherian
Copy link
Contributor Author

as @jthielen said, it does not since I never realized we used nanquantile (did we change that recently?).

I changed it in this PR. But I guess I could just revert that bit

@keewis
Copy link
Collaborator

keewis commented Jan 21, 2020

I think it's fine if you mark the failing tests as xfail

@crusaderky
Copy link
Contributor

Related: #3714

* 'master' of github.com:pydata/xarray:
  setuptools-scm and one-liner setup.py (pydata#3714)
* 'master' of github.com:pydata/xarray:
  apply_ufunc: Add meta kwarg + bump dask to 2.2 (pydata#3660)
@dcherian
Copy link
Contributor Author

This output is confusing to me. It hasn't been 6 months since bottleneck 1.3 was released. Why is that the "policy version". Similarly for zarr 2.4

Package       Required             Policy               Status
------------- -------------------- -------------------- ------
python        3.6     (2016-12-23) 3.6     (2016-12-23) =
boto3         1.9     (2018-09-10) 1.10    (2019-10-22) <
bottleneck    1.2     (2017-09-18) 1.3     (2019-11-13) <
cartopy       0.17    (2018-11-17) 0.17    (2018-11-17) =
cdms2         3.1     (2018-11-02) 3.1     (2018-11-02) =
cfgrib        0.9     (2019-02-25) 0.9     (2019-02-25) =
cftime        1.0     (2018-04-27) 1.0     (2018-04-27) =
dask          1.2     (2019-04-13) 2.2     (2019-08-01) <
distributed   1.27    (2019-04-12) 2.2     (2019-08-01) <
h5netcdf      0.7     (2019-02-27) 0.7     (2019-02-27) =
h5py          2.9     (2018-12-20) 2.10    (2019-09-10) <
hdf5          1.10    (2017-09-18) 1.10    (2017-09-18) =
iris          2.2     (2018-10-12) 2.3     (2019-12-21) <
lxml          4.4     (2019-07-27) 4.4     (2019-07-27) =
matplotlib    3.1     (2019-05-18) 3.1     (2019-05-18) =
nc-time-axis  1.2     (2019-01-25) 1.2     (2019-01-25) =
netcdf4       1.4     (2018-05-08) 1.4     (2018-05-08) =
numba         0.44    (2019-06-18) 0.46    (2019-10-25) <
numpy         1.15    (2018-07-27) 1.15    (2018-07-27) =
pandas        0.25    (2019-07-18) 0.25    (2019-07-18) =
pseudonetcdf  3.0     (2019-07-18) 3.1     (2019-10-18) <
pydap         3.2     (2018-10-16) 3.2     (2018-10-16) =
pynio         1.5     (2017-12-01) 1.5     (2017-12-01) =
rasterio      1.0     (2018-12-21) 1.1     (2019-10-15) <
scipy         1.3     (2019-05-28) 1.3     (2019-05-28) =
seaborn       0.9     (2018-07-17) 0.9     (2018-07-17) =
toolz         0.10    (2019-07-12) 0.10    (2019-07-12) =
zarr          2.3     (2019-03-25) 2.4     (2020-01-11) <

@crusaderky
Copy link
Contributor

Because NEP29 states support for all versions in the latest X months, not the most recent version released more than X months ago.

@dcherian
Copy link
Contributor Author

bumping the following seems a little excessive to me.

bottleneck    1.2     (2017-09-18) 1.3     (2019-11-13) <
iris          2.2     (2018-10-12) 2.3     (2019-12-21) <
numba         0.44    (2019-06-18) 0.46    (2019-10-25) <
pseudonetcdf  3.0     (2019-07-18) 3.1     (2019-10-18) <
rasterio      1.0     (2018-12-21) 1.1     (2019-10-15) <
zarr          2.3     (2019-03-25) 2.4     (2020-01-11) <

Is anyone opposed to merging this PR in its current form and bumping up minimum versions at the next major release?

@dcherian dcherian closed this Jan 24, 2020
@dcherian dcherian reopened this Jan 24, 2020
@crusaderky
Copy link
Contributor

I have no problems with supporting versions older than those mandated by the policy as long as there isn't any major benefit in dropping them...

@max-sixty
Copy link
Collaborator

For sure no harm in keeping older ones for this release. But to the extent we can have a policy we agree on, then it's not a judgement call each release. Should we change the policy?

@crusaderky
Copy link
Contributor

We could increase the support window for seldom-updated packages (read: not dask) to 1 year.

@dcherian
Copy link
Contributor Author

dcherian commented Jan 24, 2020

the most recent version released more than X months ago.

To me, this seems most sensible.

EDIT: crusaderky's 1 year proposal sounds good too

@dcherian dcherian merged commit 9c72866 into pydata:master Jan 24, 2020
@dcherian dcherian deleted the min-deps-15 branch January 24, 2020 21:47
dcherian added a commit to fujiisoup/xarray that referenced this pull request Jan 25, 2020
* 'master' of github.com:pydata/xarray: (27 commits)
  bump min deps for 0.15 (pydata#3713)
  setuptools-scm and isort tweaks (pydata#3720)
  Allow binned coordinates on 1D plots y-axis. (pydata#3685)
  apply_ufunc: Add meta kwarg + bump dask to 2.2 (pydata#3660)
  setuptools-scm and one-liner setup.py (pydata#3714)
  Feature/align in dot (pydata#3699)
  ENH: enable `H5NetCDFStore` to work with already open h5netcdf.File a… (pydata#3618)
  One-off isort run (pydata#3705)
  hardcoded xarray.__all__ (pydata#3703)
  Bump mypy to v0.761 (pydata#3704)
  remove DataArray and Dataset constructor deprecations for 0.15  (pydata#3560)
  Tests for variables with units (pydata#3654)
  Add an example notebook using apply_ufunc to vectorize 1D functions (pydata#3629)
  Use encoding['dtype'] over data.dtype when possible within CFMaskCoder.encode (pydata#3652)
  allow passing any iterable to drop when dropping variables (pydata#3693)
  Typo on DataSet/DataArray.to_dict documentation (pydata#3692)
  Fix mypy type checking tests failure in ds.merge (pydata#3690)
  Explicitly convert result of pd.to_datetime to a timezone-naive type (pydata#3688)
  ds.merge(da) bugfix (pydata#3677)
  fix docstring for combine_first: returns a Dataset (pydata#3683)
  ...
dcherian added a commit to dcherian/xarray that referenced this pull request Jan 27, 2020
* master:
  Add support for CFTimeIndex in get_clean_interp_index (pydata#3631)
  sel with categorical index (pydata#3670)
  bump min deps for 0.15 (pydata#3713)
  setuptools-scm and isort tweaks (pydata#3720)
  Allow binned coordinates on 1D plots y-axis. (pydata#3685)
  apply_ufunc: Add meta kwarg + bump dask to 2.2 (pydata#3660)
  setuptools-scm and one-liner setup.py (pydata#3714)
  Feature/align in dot (pydata#3699)
  ENH: enable `H5NetCDFStore` to work with already open h5netcdf.File a… (pydata#3618)
  One-off isort run (pydata#3705)
  hardcoded xarray.__all__ (pydata#3703)
  Bump mypy to v0.761 (pydata#3704)
  remove DataArray and Dataset constructor deprecations for 0.15  (pydata#3560)
  Tests for variables with units (pydata#3654)
  Add an example notebook using apply_ufunc to vectorize 1D functions (pydata#3629)
  Use encoding['dtype'] over data.dtype when possible within CFMaskCoder.encode (pydata#3652)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants