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

Fix typos found by codespell #8457

Merged
merged 1 commit into from
Nov 16, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/internals/interoperability.rst
Original file line number Diff line number Diff line change
Expand Up @@ -36,9 +36,9 @@ it is entirely possible today to:
- track the physical units of the data through computations (e.g via `pint-xarray <https://pint-xarray.readthedocs.io/en/stable/>`_),
- query the data via custom index logic optimized for specific applications (e.g. an :py:class:`~xarray.Index` object backed by a KDTree structure),
- attach domain-specific logic via accessor methods (e.g. to understand geographic Coordinate Reference System metadata),
- organize hierarchical groups of xarray data in a :py:class:`~datatree.DataTree` (e.g. to treat heterogenous simulation and observational data together during analysis).
- organize hierarchical groups of xarray data in a :py:class:`~datatree.DataTree` (e.g. to treat heterogeneous simulation and observational data together during analysis).

All of these features can be provided simultaneously, using libaries compatible with the rest of the scientific python ecosystem.
All of these features can be provided simultaneously, using libraries compatible with the rest of the scientific python ecosystem.
In this situation xarray would be essentially a thin wrapper acting as pure-python framework, providing a common interface and
separation of concerns via various domain-agnostic abstractions.

Expand Down
2 changes: 1 addition & 1 deletion xarray/core/dataset.py
Original file line number Diff line number Diff line change
Expand Up @@ -10075,7 +10075,7 @@ def groupby(
Tutorial on :py:func:`~xarray.Dataset.Groupby` for windowed computation.

:doc:`xarray-tutorial:fundamentals/03.2_groupby_with_xarray`
Tutorial on :py:func:`~xarray.Dataset.Groupby` demonstrating reductions, transformation and comparision with :py:func:`~xarray.Dataset.resample`.
Tutorial on :py:func:`~xarray.Dataset.Groupby` demonstrating reductions, transformation and comparison with :py:func:`~xarray.Dataset.resample`.

Dataset.groupby_bins
DataArray.groupby
Expand Down
2 changes: 1 addition & 1 deletion xarray/tests/test_duck_array_ops.py
Original file line number Diff line number Diff line change
Expand Up @@ -500,7 +500,7 @@ def test_reduce(dim_num, dtype, dask, func, skipna, aggdim):
expected = getattr(da.compute(), func)(skipna=skipna, dim=aggdim)
assert_allclose(actual, expected, rtol=rtol)

# make sure the compatiblility with pandas' results.
# make sure the compatibility with pandas' results.
if func in ["var", "std"]:
expected = series_reduce(da, func, skipna=skipna, dim=aggdim, ddof=0)
assert_allclose(actual, expected, rtol=rtol)
Expand Down
2 changes: 1 addition & 1 deletion xarray/util/generate_aggregations.py
Original file line number Diff line number Diff line change
Expand Up @@ -350,7 +350,7 @@ def generate_method(self, method):

yield TEMPLATE_RETURNS.format(**template_kwargs)

# we want Datset.count to refer to DataArray.count
# we want Dataset.count to refer to DataArray.count
# but we also want DatasetGroupBy.count to refer to Dataset.count
# The generic aggregations have self.cls == ''
others = (
Expand Down
Loading