Bump the python group across 1 directory with 4 updates

[dependabot]

Updates the requirements on fsspec[http], tzdata, xarray and zarr to permit the latest version.
Updates fsspec[http] to 2025.2.0

Commits

• f30bc75 changelog (#1786)
• 7cc1644 referencefs: add streaming _open support (#1778)
• 08d1e49 Cope with zarr3 Buffers in referenceFS (#1784)
• fe59f48 drop dask-expr dependency from downstream tests (#1781)
• 375a411 use codespell pre-commit hook (#1780)
• 5163ac7 spec: fix spelling error in docstring for fs.walk (#1779)
• 3763661 asyn_wrapper: avoid creating async version of open method (#1769)
• 216885a pre-commit autoupdate (#1774)
• 30af5e1 Add newline inclusive disclaimer (#1770)
• 1d34249 Use operator.itemgetter for perf/readability in archive (#1764)
• Additional commits viewable in compare view

Updates tzdata to 2025.1

Release notes

Sourced from tzdata's releases.

2025.1: Release of upstream tzdata 2025a

Version 2025.1

Upstream version 2025a released 2025-01-15T18:47:24+00:00

Briefly:

Paraguay adopts permanent -03 starting spring 2024. Improve pre-1991 data for the Philippines. Etc/Unknown is now reserved.

Changes to future timestamps

Paraguay will stop changing its clocks after the spring-forward transition on 2024-10-06, so it is now permanently at -03. (Thanks to Heitor David Pinto and Even Scharning.) This affects timestamps starting 2025-03-22, as well as the obsolescent tm_isdst flags starting 2024-10-15.

Changes to past timestamps

Correct timestamps for the Philippines before 1900, and from 1937 through 1990. (Thanks to P Chan for the heads-up and citations.) This includes adjusting local mean time before 1899; fixing transitions in September 1899, January 1937, and June 1954; adding transitions in December 1941, November 1945, March and September 1977, and May and July 1990; and removing incorrect transitions in March and September 1978.

Changes to data

Add zone1970.tab lines for the Concordia and Eyre Bird Observatory research stations. (Thanks to Derick Rethans and Jule Dabars.)

Changes to documentation

The name Etc/Unknown is now reserved: it will not be used by TZDB. This is for compatibility with CLDR, which uses the string "Etc/Unknown" for an unknown or invalid timezone. (Thanks to Justin Grant, Mark Davis, and Guy Harris.)

Cite Internet RFC 9636, which obsoletes RFC 8536 for TZif format.

Changelog

Sourced from tzdata's changelog.

Version 2025.1

Upstream version 2025a released 2025-01-15T18:47:24+00:00

Briefly:

Paraguay adopts permanent -03 starting spring 2024. Improve pre-1991 data for the Philippines. Etc/Unknown is now reserved.

Changes to future timestamps

Paraguay will stop changing its clocks after the spring-forward transition on 2024-10-06, so it is now permanently at -03. (Thanks to Heitor David Pinto and Even Scharning.) This affects timestamps starting 2025-03-22, as well as the obsolescent tm_isdst flags starting 2024-10-15.

Changes to past timestamps

Correct timestamps for the Philippines before 1900, and from 1937 through 1990. (Thanks to P Chan for the heads-up and citations.) This includes adjusting local mean time before 1899; fixing transitions in September 1899, January 1937, and June 1954; adding transitions in December 1941, November 1945, March and September 1977, and May and July 1990; and removing incorrect transitions in March and September 1978.

Changes to data

Add zone1970.tab lines for the Concordia and Eyre Bird Observatory research stations. (Thanks to Derick Rethans and Jule Dabars.)

Changes to documentation

The name Etc/Unknown is now reserved: it will not be used by TZDB. This is for compatibility with CLDR, which uses the string "Etc/Unknown" for an unknown or invalid timezone. (Thanks to Justin Grant, Mark Davis, and Guy Harris.)

Cite Internet RFC 9636, which obsoletes RFC 8536 for TZif format.

---

Version 2024.2

Upstream version 2024b released 2024-09-04T19:27:47+00:00

Briefly:

Improve historical data for Mexico, Mongolia, and Portugal. System V names are now obsolescent. The main data form now uses %z. The code now conforms to RFC 8536 for early timestamps. Support POSIX.1-2024, which removes asctime_r and ctime_r. Assume POSIX.2-1992 or later for shell scripts. SUPPORT_C89 now defaults to 1.

... (truncated)

Commits

• 0ccabea Bump release to 2025.1
• d0078ca Update tzdata to version '2025a'
• 5bf324b Use proper syntax for multiline env variable
• a178a14 Fix setup_cfg_fmt pre-commit environment
• 1397de8 Update pre-commit config
• 0cce78d Add automatic PR action
• 3b721cd Don't update the repo unless we need to
• d913020 Update tzdata to 2024b
• fdd075c Remove POSIXRULES= from make invocation
• See full diff in compare view

Updates xarray to 2025.1.2

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. First fetch all previous release tags so we can see the version number of the last release was:

   git fetch upstream --tags

   Then run

   python ci/release_contributors.py

   (needs gitpython and toolz / cytoolz)

   and copy the output.

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.

... (truncated)

Commits

• d8d1d9e release notes: 2025.01.2 (#10007)
• 326dbe7 Add FAQ answer about API stability & backwards compatibility (#9855)
• 5b3f127 Preserve order of variables in combine_by_coords (#9070)
• 97a4a71 fix typing (#10006)
• f91306a cast numpy scalars to arrays in NamedArray.from_array (#10008)
• e84e421 Use freq='D' instead of freq='d' in pd.timedelta_range (#10004)
• d7ac79a Fix the push method when the limit parameter is bigger than the chunk… (#9940)
• 5fdceff Migrate Zarr region="auto" tests to a class (#9990)
• 018b241 Fix infer_freq, check for subdtype "datetime64"/"timedelta64" (#9999)
• 8ccf1cb Revert "Use flox for grouped first, last (#9986)" (#10001)
• Additional commits viewable in compare view

Updates zarr to 3.0.4

Release notes

Sourced from zarr's releases.

v3.0.4

What's Changed

• Unnecessary lambda expression by @​DimitriPapadopoulos in zarr-developers/zarr-python#2828
• don't serialize empty tuples for v2 filters, and warn when reading such metadata by @​d-v-b in zarr-developers/zarr-python#2847
• Fix a bug when setting complete chunks by @​dcherian in zarr-developers/zarr-python#2851
• feat/batch creation by @​d-v-b in zarr-developers/zarr-python#2665

Full Changelog: zarr-developers/zarr-python@v3.0.3...v3.0.4

Changelog

Sourced from zarr's changelog.

Release notes

.. towncrier release notes start

3.0.3 (2025-02-14)

Features

- Improves performance of FsspecStore.delete_dir for remote filesystems supporting concurrent/batched deletes, e.g., s3fs. (:issue:`2661`)
- Added :meth:`zarr.config.enable_gpu` to update Zarr's configuration to use GPUs. (:issue:`2751`)
- Avoid reading chunks during writes where possible. :issue:`757` (:issue:`2784`)
- :py:class:`LocalStore` learned to ``delete_dir``. This makes array and group deletes more efficient. (:issue:`2804`)
- Add `zarr.testing.strategies.array_metadata` to generate ArrayV2Metadata and ArrayV3Metadata instances. (:issue:`2813`)
- Add arbitrary `shards` to Hypothesis strategy for generating arrays. (:issue:`2822`)
Bugfixes

• Fixed bug with Zarr using device memory, instead of host memory, for storing metadata when using GPUs. (:issue:2751)
• The array returned by zarr.empty and an empty zarr.core.buffer.cpu.NDBuffer will now be filled with the specified fill value, or with zeros if no fill value is provided. This fixes a bug where Zarr format 2 data with no fill value was written with un-predictable chunk sizes. (:issue:2755)
• Fix zip-store path checking for stores with directories listed as files. (:issue:2758)
• Use removeprefix rather than replace when removing filename prefixes in FsspecStore.list (:issue:2778)
• Enable automatic removal of needs release notes with labeler action (:issue:2781)
• Use the proper label config (:issue:2785)
• Alters the behavior of create_array to ensure that any groups implied by the array's name are created if they do not already exist. Also simplifies the type signature for any function that takes an ArrayConfig-like object. (:issue:2795)
• Enitialise empty chunks to the default fill value during writing and add default fill values for datetime, timedelta, structured, and other (void* fixed size) data types (:issue:2799)
• Ensure utf8 compliant strings are used to construct numpy arrays in property-based tests (:issue:2801)
• Fix pickling for ZipStore (:issue:2807)
• Update numcodecs to not overwrite codec configuration ever. Closes :issue:2800. (:issue:2811)
• Fix fancy indexing (e.g. arr[5, [0, 1]]) with the sharding codec (:issue:2817)

Improved Documentation

- Added new user guide on :ref:`user-guide-gpu`. (:issue:`2751`)
3.0.2 (2025-01-31)
Features

</tr></table> 
</code></pre>
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>

<li><a href="https://github.com/zarr-developers/zarr-python/commit/8d2fb47252a7ed5eb163ccfb0401e4e0486f72f6&quot;&gt;&lt;code&gt;8d2fb47&lt;/code&gt;&lt;/a> feat/batch creation (<a href="https://redirect.github.com/zarr-developers/zarr-python/issues/2665&quot;&gt;#2665&lt;/a&gt;)&lt;/li>

<li><a href="https://github.com/zarr-developers/zarr-python/commit/8b59a38463dca7b3c908aa3db7d5321a80a3c285&quot;&gt;&lt;code&gt;8b59a38&lt;/code&gt;&lt;/a> Fix a bug when setting complete chunks (<a href="https://redirect.github.com/zarr-developers/zarr-python/issues/2851&quot;&gt;#2851&lt;/a&gt;)&lt;/li>

<li><a href="https://github.com/zarr-developers/zarr-python/commit/96c967786c42e235f4d07dfcdd2a3a72bcd508e1&quot;&gt;&lt;code&gt;96c9677&lt;/code&gt;&lt;/a> don't serialize empty tuples for v2 filters, and warn when reading such metad...</li>

<li><a href="https://github.com/zarr-developers/zarr-python/commit/e8bfb6484aeb543c21b9b0f6de2e0f0a034fc5d7&quot;&gt;&lt;code&gt;e8bfb64&lt;/code&gt;&lt;/a> Unnecessary lambda expression (<a href="https://redirect.github.com/zarr-developers/zarr-python/issues/2828&quot;&gt;#2828&lt;/a&gt;)&lt;/li>

<li><a href="https://github.com/zarr-developers/zarr-python/commit/5a36e175325c1f6e55b0638009b8aa7e5ab89a05&quot;&gt;&lt;code&gt;5a36e17&lt;/code&gt;&lt;/a> Changelog for v3.0.3 (<a href="https://redirect.github.com/zarr-developers/zarr-python/issues/2836&quot;&gt;#2836&lt;/a&gt;)&lt;/li>

<li><a href="https://github.com/zarr-developers/zarr-python/commit/8ad4cd69335a32d85b0b1c380572596b1e9f26b7&quot;&gt;&lt;code&gt;8ad4cd6&lt;/code&gt;&lt;/a> Run fsspec tests in min_deps env (<a href="https://redirect.github.com/zarr-developers/zarr-python/issues/2835&quot;&gt;#2835&lt;/a&gt;)&lt;/li>

<li><a href="https://github.com/zarr-developers/zarr-python/commit/48f7c9af3b49e3221c65c3447e869437c0fb7575&quot;&gt;&lt;code&gt;48f7c9a&lt;/code&gt;&lt;/a> Feat: improves delete_dir for s3fs-backed FsspecStore (<a href="https://redirect.github.com/zarr-developers/zarr-python/issues/2661&quot;&gt;#2661&lt;/a&gt;)&lt;/li>

<li><a href="https://github.com/zarr-developers/zarr-python/commit/23abb5b0cfb8b9565985e7e682a498405d630b34&quot;&gt;&lt;code&gt;23abb5b&lt;/code&gt;&lt;/a> Add more setitem property tests (<a href="https://redirect.github.com/zarr-developers/zarr-python/issues/2825&quot;&gt;#2825&lt;/a&gt;)&lt;/li>

<li><a href="https://github.com/zarr-developers/zarr-python/commit/f8bc3153162e85ad41f62cdb6c693239868b85c6&quot;&gt;&lt;code&gt;f8bc315&lt;/code&gt;&lt;/a> create_array creates explicit groups (<a href="https://redirect.github.com/zarr-developers/zarr-python/issues/2795&quot;&gt;#2795&lt;/a&gt;)&lt;/li>

<li><a href="https://github.com/zarr-developers/zarr-python/commit/3c25dacdd41e9a67f32c2cfac364292bb34d9370&quot;&gt;&lt;code&gt;3c25dac&lt;/code&gt;&lt;/a> Add shards to array strategy (<a href="https://redirect.github.com/zarr-developers/zarr-python/issues/2822&quot;&gt;#2822&lt;/a&gt;)&lt;/li>

<li>Additional commits viewable in <a href="https://github.com/zarr-developers/zarr-python/compare/v2.13.0...v3.0.4&quot;&gt;compare view</a></li>

</ul>

</details>
<br />


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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions