Bump xarray from 0.16.0 to 2023.1.0

[dependabot]

Bumps xarray from 0.16.0 to 2023.1.0.

Release notes

Sourced from xarray's releases.

v2023.01.0

See https://docs.xarray.dev/en/stable/whats-new.html

v2022.12.0

This release includes a number of bug fixes and experimental support for Zarr V3. Thanks to the 16 contributors to this release: Deepak Cherian, Francesco Zanetta, Gregory Lee, Illviljan, Joe Hamman, Justus Magin, Luke Conibear, Mark Harfouche, Mathias Hauser, Mick, Mike Taves, Sam Levang, Spencer Clark, Tom Nicholas, Wei Ji, templiert

New Features

• Enable using offset and origin arguments in :py:meth:DataArray.resample and :py:meth:Dataset.resample (:issue:7266, :pull:7284). By Spencer Clark <https://github.com/spencerkclark>_.
• Add experimental support for Zarr's in-progress V3 specification. (:pull:6475). By Gregory Lee <https://github.com/grlee77>_ and Joe Hamman <https://github.com/jhamman>_.

Breaking changes

• The minimum versions of some dependencies were changed (:pull:7300):

  ========================== ========= ======== Package Old New ========================== ========= ======== boto 1.18 1.20 cartopy 0.19 0.20 distributed 2021.09 2021.11 dask 2021.09 2021.11 h5py 3.1 3.6 hdf5 1.10 1.12 matplotlib-base 3.4 3.5 nc-time-axis 1.3 1.4 netcdf4 1.5.3 1.5.7 packaging 20.3 21.3 pint 0.17 0.18 pseudonetcdf 3.1 3.2 typing_extensions 3.10 4.0 ========================== ========= ========

Deprecations

• The PyNIO backend has been deprecated (:issue:4491, :pull:7301). By Joe Hamman <https://github.com/jhamman>_.

Bug fixes

• Fix handling of coordinate attributes in :py:func:where. (:issue:7220, :pull:7229) By Sam Levang <https://github.com/slevang>_.
• Import nc_time_axis when needed (:issue:7275, :pull:7276). By Michael Niklas <https://github.com/headtr1ck>_.
• Fix static typing of :py:meth:xr.polyval (:issue:7312, :pull:7315). By Michael Niklas <https://github.com/headtr1ck>_.
• Fix multiple reads on fsspec S3 files by resetting file pointer to 0 when reading file streams (:issue:6813, :pull:7304).

... (truncated)

Changelog

Sourced from xarray's changelog.

How to issue an xarray release in 16 easy steps

Time required: about an hour.

These instructions assume that upstream refers to the main repository:

$ git remote -v
{...}
upstream        https://github.com/pydata/xarray (fetch)
upstream        https://github.com/pydata/xarray (push)

1. Ensure your main branch is synced to upstream:

   git switch main
   git pull upstream main

2. Add a list of contributors with:

   git log "$(git tag --sort=v:refname | tail -1).." --format=%aN | sort -u | perl -pe 's/\n/$1, /'

   This will return the number of contributors:

   git log "$(git tag --sort=v:refname | tail -1).." --format=%aN | sort -u | wc -l

3. Write a release summary: ~50 words describing the high level features. This will be used in the release emails, tweets, GitHub release notes, etc.
4. Look over whats-new.rst and the docs. Make sure "What's New" is complete (check the date!) and add the release summary at the top. Things to watch out for:
   • Important new features should be highlighted towards the top.
   • Function/method references should include links to the API docs.
   • Sometimes notes get added in the wrong section of whats-new, typically due to a bad merge. Check for these before a release by using git diff, e.g., git diff v{YYYY.MM.X-1} whats-new.rst where {YYYY.MM.X-1} is the previous release.
5. Open a PR with the release summary and whatsnew changes; in particular the release headline should get feedback from the team on what's important to include.
6. After merging, again ensure your main branch is synced to upstream:

   git pull upstream main

7. If you have any doubts, run the full test suite one final time!

   pytest

8. Check that the ReadTheDocs build is passing on the main branch.

... (truncated)

Commits

• d0bfd00 v2023.01.0 whats-new (#7440)
• 522ee22 explain keep_attrs in docstring of apply_ufunc (#7445)
• b741d83 Add sentence to open_dataset docstring (#7438)
• b589f6b pin scipy version in doc environment (#7436)
• 6c5840e Improve performance for backend datetime handling (#7374)
• 4f3128b fix typo (#7433)
• 17933e7 Add lazy backend ASV test (#7426)
• f3b7c69 Pull Request Labeler - Workaround sync-labels bug (#7431)
• 2ef82c5 see also : groupby in resample doc and vice-versa (#7425)
• d6d2450 Some alignment optimizations (#7382)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Dependabot tried to add @jsnel as a reviewer to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/admdev8/pyglotaran/pulls/191/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the admdev8/pyglotaran repository. // See: https://docs.github.com/rest/reference/pulls#request-reviewers-for-a-pull-request

[performance-testing-bot]

Unable to locate .performanceTestingBot config file

[vizipi]

Pull request analysis by VIZIPI

Below you will find who is the most qualified team member to review your code.
This analysis includes his/her work on the code included in this Pull request, in addition to their experience in code affected by these changes ( partly found within the list of potential missing files below )   Feedback always welcome

No other active qualified developers found to review these specific changes. You might consider involving more team members with these code segments.

---

Potential missing files from this Pull request

No commonly committed files found with a 40% threashold

---

Committed file ranks

(click to expand)

99.95%[requirements_dev.txt]