html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/pull/4314#issuecomment-676670722,https://api.github.com/repos/pydata/xarray/issues/4314,676670722,MDEyOklzc3VlQ29tbWVudDY3NjY3MDcyMg==,2448579,2020-08-19T20:34:29Z,2020-08-19T20:34:29Z,MEMBER,Thanks @dnowacki-usgs ,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-670769986,https://api.github.com/repos/pydata/xarray/issues/4314,670769986,MDEyOklzc3VlQ29tbWVudDY3MDc2OTk4Ng==,24736507,2020-08-07T22:32:23Z,2020-08-19T19:20:14Z,NONE,"Hello @dnowacki-usgs! Thanks for updating this PR. We checked the lines you've touched for [PEP 8](https://www.python.org/dev/peps/pep-0008) issues, and found:













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

##### Comment last updated at 2020-08-19 19:20:14 UTC","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-676589767,https://api.github.com/repos/pydata/xarray/issues/4314,676589767,MDEyOklzc3VlQ29tbWVudDY3NjU4OTc2Nw==,14808389,2020-08-19T18:30:34Z,2020-08-19T18:30:34Z,MEMBER,"I've opened a PR to update the guide, hopefully that helps.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-676579147,https://api.github.com/repos/pydata/xarray/issues/4314,676579147,MDEyOklzc3VlQ29tbWVudDY3NjU3OTE0Nw==,13837821,2020-08-19T18:08:12Z,2020-08-19T18:09:33Z,CONTRIBUTOR,"Ah, I see, `merge` instead of `rebase`. I'll try that next time.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-676576773,https://api.github.com/repos/pydata/xarray/issues/4314,676576773,MDEyOklzc3VlQ29tbWVudDY3NjU3Njc3Mw==,14808389,2020-08-19T18:03:23Z,2020-08-19T18:03:23Z,MEMBER,"I think it should be
```sh
git checkout master
git pull
git checkout <feature-branch>
git merge master
git push
```
or
```sh
git fetch upstream
git merge upstream/master
git push
```
instead","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-676575840,https://api.github.com/repos/pydata/xarray/issues/4314,676575840,MDEyOklzc3VlQ29tbWVudDY3NjU3NTg0MA==,14808389,2020-08-19T18:01:22Z,2020-08-19T18:01:22Z,MEMBER,"ah, now I understand where the duplication is coming from. I'm guessing you did that and then tried to push, but it complained about different commits, so you pulled and then pushed.

I fixed it for you.

I think we should update that guide, rebasing is usually not a good idea because then you'd have to force-push, too (and github doesn't handle force-pushing that well).","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-676571966,https://api.github.com/repos/pydata/xarray/issues/4314,676571966,MDEyOklzc3VlQ29tbWVudDY3NjU3MTk2Ng==,13837821,2020-08-19T17:53:14Z,2020-08-19T17:53:55Z,CONTRIBUTOR,"Ugh, sorry about that. I'm following the instructions in [contributing to xarray](http://xarray.pydata.org/en/stable/contributing.html#creating-a-branch). It's a fetch/rebase. Happy to do it another way if there is a better practice. Thanks.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-676563830,https://api.github.com/repos/pydata/xarray/issues/4314,676563830,MDEyOklzc3VlQ29tbWVudDY3NjU2MzgzMA==,14808389,2020-08-19T17:35:57Z,2020-08-19T17:38:46Z,MEMBER,"which command did you use to create the merge? I think that was some sort of rebase merge, which means that all merged commits are included in the commit history, and github doesn't seem to work well with this kind of merges. You also have duplicated commits in the history, which confuses me.

Edit: it seems you somehow merged / rebased the branch onto itself. Just as reference, I usually use
```sh
git checkout master
git pull
git checkout <feature-branch>
git merge master
git push
```
for merging","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-676554163,https://api.github.com/repos/pydata/xarray/issues/4314,676554163,MDEyOklzc3VlQ29tbWVudDY3NjU1NDE2Mw==,14808389,2020-08-19T17:16:35Z,2020-08-19T17:16:35Z,MEMBER,could you merge in `master`? I think that would fix the failing build.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-676548419,https://api.github.com/repos/pydata/xarray/issues/4314,676548419,MDEyOklzc3VlQ29tbWVudDY3NjU0ODQxOQ==,13837821,2020-08-19T17:05:33Z,2020-08-19T17:06:29Z,CONTRIBUTOR,"Updated the try/except following @keewis's lead. Also sparse 0.11.0 has been released so I was able to check that the warning is correctly issued for 0.10.0, then I upgraded, and the warning is no longer issued (and sparse doesn't choke on the casting kwarg).","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-676539274,https://api.github.com/repos/pydata/xarray/issues/4314,676539274,MDEyOklzc3VlQ29tbWVudDY3NjUzOTI3NA==,5635139,2020-08-19T16:47:02Z,2020-08-19T16:47:02Z,MEMBER,"I just saw I was up for reviewing this — sorry for missing that.

Looks good. @keewis 's suggestion for the back-compat code looks like a nice refinement — it includes a version check which will ease disentangling it. Could we add that and then merge?","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-673746915,https://api.github.com/repos/pydata/xarray/issues/4314,673746915,MDEyOklzc3VlQ29tbWVudDY3Mzc0NjkxNQ==,14808389,2020-08-13T22:47:01Z,2020-08-19T16:10:03Z,MEMBER,"I think that was due to a rebase merge (?). I fixed the commit history using cherry-picking and force-pushed to your branch, but there's a [backup of the old branch](https://github.com/pydata/xarray/tree/astypekeepattrs-backup) if something went wrong.

@dnowacki-usgs, if you want to add new commits you'll first have to force-pull (or delete your local branch and check out the remote branch – just make sure that you don't lose any unpushed commits).","{""total_count"": 3, ""+1"": 3, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-674191679,https://api.github.com/repos/pydata/xarray/issues/4314,674191679,MDEyOklzc3VlQ29tbWVudDY3NDE5MTY3OQ==,13837821,2020-08-14T17:52:52Z,2020-08-14T17:52:52Z,CONTRIBUTOR,Thanks for the review @dcherian. I modified the tests as suggested and added some docstring updates. Let me know what you think.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-673727756,https://api.github.com/repos/pydata/xarray/issues/4314,673727756,MDEyOklzc3VlQ29tbWVudDY3MzcyNzc1Ng==,5635139,2020-08-13T21:50:15Z,2020-08-13T21:50:15Z,MEMBER,"There are some duplicated commits — 3x `Recreate gaj...` — though still weird that GH and git disagree.

I'd suggest the squash and push -f...

```
*   e23529e0 - (HEAD -> astypekeepattrs, dnowacki-usgs/astypekeepattrs, pr/dnowacki-usgs/4314) Merge branch 'astypekeepattrs' of https://github.com/dnowacki-usgs/xarray into astypekeepattrs (3 hours ago) <Dan Nowacki>
|\
| * ac42be80 - improve error handling and check if sparse array (6 days ago) <Dan Nowacki>
| * e2d38550 - fix dtype test (7 days ago) <Dan Nowacki>
| *   e079cf86 - Merge branch 'astypekeepattrs' of https://github.com/dnowacki-usgs/xarray into astypekeepattrs (7 days ago) <Dan Nowacki>
| |\
| | *   1296f590 - Merge branch 'master' into pr/dnowacki-usgs/4314 (8 days ago) <Maximilian Roos>
| | |\
| | * | 5c101d85 - Accept keep_attrs flag, use apply_ufunc in variable.py, expand tests (8 days ago) <Dan Nowacki>
| | * | d75e1fb9 - Recreate @gajomi's #2070 to keep attrs when calling astype() (8 days ago) <Dan Nowacki>
| * | | eb86c8a6 - add to whats new (7 days ago) <Dan Nowacki>
| * | | db014baf - Ignore casting if we get a TypeError (indicates sparse <= 0.10.0) (7 days ago) <Dan Nowacki>
| * | | 01d1b378 - Accept keep_attrs flag, use apply_ufunc in variable.py, expand tests (7 days ago) <Dan Nowacki>
| * | | 00bfeaa3 - Recreate @gajomi's #2070 to keep attrs when calling astype() (7 days ago) <Dan Nowacki>
* | | | dba93b18 - improve error handling and check if sparse array (3 hours ago) <Dan Nowacki>
* | | | 4856eec5 - fix dtype test (3 hours ago) <Dan Nowacki>
* | | | 983f17d5 - add to whats new (3 hours ago) <Dan Nowacki>
* | | | 9f9b06c6 - Ignore casting if we get a TypeError (indicates sparse <= 0.10.0) (3 hours ago) <Dan Nowacki>
* | | | a277c2a4 - Accept keep_attrs flag, use apply_ufunc in variable.py, expand tests (3 hours ago) <Dan Nowacki>
* | | | 833e444f - Recreate @gajomi's #2070 to keep attrs when calling astype() (3 hours ago) <Dan Nowacki>
* | | | 7ee97989 - Accept keep_attrs flag, use apply_ufunc in variable.py, expand tests (4 hours ago) <Dan Nowacki>
* | | | dd4f5494 - Recreate @gajomi's #2070 to keep attrs when calling astype() (4 hours ago) <Dan Nowacki>
* | | | 7daad4fc - (upstream/master, upstream/HEAD, origin/master, master) Implement interp for interpolating between chunks of data (dask) (#4155) (2 days ago) <Alexandre Poux>
* | | | d514b120 - Add @mathause to current core developers. (#4335) (2 days ago) <Deepak Cherian>
* | | | ceadecd5 - install sphinx-autosummary-accessors from conda-forge (#4332) (3 days ago) <keewis>
* | | | 1791c3b6 - Use sphinx-accessors-autosummary (#4323) (4 days ago) <keewis>
* | | | df7b2eae - ndrolling fixes (#4329) (4 days ago) <Keisuke Fujii>
* | | | f02ca537 - DOC: fix typo argmin -> argmax in DataArray.argmax docstring (#4327) (5 days ago) <Sander>
* | | | 6e9edff5 - pin sphinx to 3.1(#4326) (5 days ago) <keewis>
* | | | 1d3dee08 - nd-rolling (#4219) (6 days ago) <Keisuke Fujii>
|/ / /
* | | e04e21d6 - Implicit dask import 4164 (#4318) (7 days ago) <inakleinbottle>
* | | 7ba19e12 - allow customizing the inline repr of a duck array (#4248) (7 days ago) <keewis>
| |/
|/|
* | 98dc1f4e - silence the known docs CI issues (#4316) (8 days ago) <keewis>
* | ed6fff2c - enh: fixed #4302 (#4315) (8 days ago) <Nick R. Papior>
* | 1101eca6 - Remove all unused and warn-raising methods from AbstractDataStore (#4310) (8 days ago) <alexamici>
|/
* e1dafe67 - (dnowacki-usgs/master) Fix map_blocks example (#4305) (10 days ago) <Tom Augspurger>
```","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-673724685,https://api.github.com/repos/pydata/xarray/issues/4314,673724685,MDEyOklzc3VlQ29tbWVudDY3MzcyNDY4NQ==,5635139,2020-08-13T21:41:40Z,2020-08-13T21:41:40Z,MEMBER,"The weirdest part is that the local diff is fine; here's the output of `git --no-pager diff upstream/master`. Is it maybe because one of the merge commits was mine rather than @dnowacki-usgs ? 

Sorry if I contributed to this.

One override is to apply this patch on master and force push this branch. I'm happy to do it if @dnowacki-usgs agrees.

<details>

```diff
diff --git a/doc/whats-new.rst b/doc/whats-new.rst
index 793f72fb..4b7b117b 100644
--- a/doc/whats-new.rst
+++ b/doc/whats-new.rst
@@ -21,7 +21,9 @@ v0.16.1 (unreleased)
 
 Breaking changes
 ~~~~~~~~~~~~~~~~
-
+- :py:meth:`DataArray.astype` and :py:meth:`Dataset.astype` now preserve attributes. Keep the
+  old behavior by passing `keep_attrs=False` (:issue:`2049`, :pull:`4314`).
+  By `Dan Nowacki <https://github.com/dnowacki-usgs>`_ and `Gabriel Joel Mitchell <https://github.com/gajomi>`_.
 
 New Features
 ~~~~~~~~~~~~
diff --git a/xarray/core/common.py b/xarray/core/common.py
index bc5035b6..7b6fc13c 100644
--- a/xarray/core/common.py
+++ b/xarray/core/common.py
@@ -1305,6 +1305,48 @@ class DataWithCoords(SupportsArithmetic, AttrAccessMixin):
             dask=""allowed"",
         )
 
+    def astype(self, dtype, casting=""unsafe"", copy=True, keep_attrs=True):
+        """"""
+        Copy of the xarray object, with data cast to a specified type.
+        Leaves coordinate dtype unchanged.
+
+        Parameters
+        ----------
+        dtype : str or dtype
+            Typecode or data-type to which the array is cast.
+        casting : {'no', 'equiv', 'safe', 'same_kind', 'unsafe'}, optional
+            Controls what kind of data casting may occur. Defaults to 'unsafe'
+            for backwards compatibility.
+
+            * 'no' means the data types should not be cast at all.
+            * 'equiv' means only byte-order changes are allowed.
+            * 'safe' means only casts which can preserve values are allowed.
+            * 'same_kind' means only safe casts or casts within a kind,
+                like float64 to float32, are allowed.
+            * 'unsafe' means any data conversions may be done.
+        copy : bool, optional
+            By default, astype always returns a newly allocated array. If this
+            is set to False and the `dtype` requirement is satisfied, the input
+            array is returned instead of a copy.
+        keep_attrs : bool, optional
+            By default, astype keeps attributes. Set to False to remove
+            attributes in the returned object.
+
+        See also
+        --------
+        np.ndarray.astype
+        dask.array.Array.astype
+        """"""
+        from .computation import apply_ufunc
+
+        return apply_ufunc(
+            duck_array_ops.astype,
+            self,
+            kwargs=dict(dtype=dtype, casting=casting, copy=copy),
+            keep_attrs=keep_attrs,
+            dask=""allowed"",
+        )
+
     def __enter__(self: T) -> T:
         return self
 
diff --git a/xarray/core/duck_array_ops.py b/xarray/core/duck_array_ops.py
index 3d192882..7b28d396 100644
--- a/xarray/core/duck_array_ops.py
+++ b/xarray/core/duck_array_ops.py
@@ -149,6 +149,33 @@ masked_invalid = _dask_or_eager_func(
 )
 
 
+def astype(data, **kwargs):
+    try:
+        return data.astype(**kwargs)
+    except TypeError as e:
+        # FIXME: This should no longer be necessary in future versions of sparse
+        # Current versions of sparse (v0.10.0) don't support the ""casting"" kwarg
+        # This was fixed by https://github.com/pydata/sparse/pull/392
+        try:
+            import sparse
+        except ImportError:
+            sparse = None
+        if (
+            ""got an unexpected keyword argument 'casting'"" in repr(e)
+            and sparse is not None
+            and isinstance(data, sparse._coo.core.COO)
+        ):
+            warnings.warn(
+                ""The current version of sparse does not support the 'casting' argument. It will be ignored in the call to astype()."",
+                RuntimeWarning,
+                stacklevel=4,
+            )
+            kwargs.pop(""casting"")
+        else:
+            raise e
+        return data.astype(**kwargs)
+
+
 def asarray(data, xp=np):
     return (
         data
diff --git a/xarray/core/ops.py b/xarray/core/ops.py
index 36753179..dad37f3b 100644
--- a/xarray/core/ops.py
+++ b/xarray/core/ops.py
@@ -42,7 +42,7 @@ NUM_BINARY_OPS = [
 NUMPY_SAME_METHODS = [""item"", ""searchsorted""]
 # methods which don't modify the data shape, so the result should still be
 # wrapped in an Variable/DataArray
-NUMPY_UNARY_METHODS = [""astype"", ""argsort"", ""clip"", ""conj"", ""conjugate""]
+NUMPY_UNARY_METHODS = [""argsort"", ""clip"", ""conj"", ""conjugate""]
 PANDAS_UNARY_FUNCTIONS = [""isnull"", ""notnull""]
 # methods which remove an axis
 REDUCE_METHODS = [""all"", ""any""]
diff --git a/xarray/core/variable.py b/xarray/core/variable.py
index 1f86a403..6d53a4fe 100644
--- a/xarray/core/variable.py
+++ b/xarray/core/variable.py
@@ -360,6 +360,47 @@ class Variable(
             )
         self._data = data
 
+    def astype(self, dtype, casting=""unsafe"", copy=True, keep_attrs=True):
+        """"""
+        Copy of the Variable object, with data cast to a specified type.
+
+        Parameters
+        ----------
+        dtype : str or dtype
+             Typecode or data-type to which the array is cast.
+        casting : {'no', 'equiv', 'safe', 'same_kind', 'unsafe'}, optional
+             Controls what kind of data casting may occur. Defaults to 'unsafe'
+             for backwards compatibility.
+
+             * 'no' means the data types should not be cast at all.
+             * 'equiv' means only byte-order changes are allowed.
+             * 'safe' means only casts which can preserve values are allowed.
+             * 'same_kind' means only safe casts or casts within a kind,
+                 like float64 to float32, are allowed.
+             * 'unsafe' means any data conversions may be done.
+        copy : bool, optional
+             By default, astype always returns a newly allocated array. If this
+             is set to False and the `dtype` requirement is satisfied, the input
+             array is returned instead of a copy.
+        keep_attrs : bool, optional
+            By default, astype keeps attributes. Set to False to remove
+            attributes in the returned object.
+
+        See also
+        --------
+        np.ndarray.astype
+        dask.array.Array.astype
+        """"""
+        from .computation import apply_ufunc
+
+        return apply_ufunc(
+            duck_array_ops.astype,
+            self,
+            kwargs=dict(dtype=dtype, casting=casting, copy=copy),
+            keep_attrs=keep_attrs,
+            dask=""allowed"",
+        )
+
     def load(self, **kwargs):
         """"""Manually trigger loading of this variable's data from disk or a
         remote source into memory and return this variable.
diff --git a/xarray/tests/test_dataarray.py b/xarray/tests/test_dataarray.py
index f10404d7..77969e5c 100644
--- a/xarray/tests/test_dataarray.py
+++ b/xarray/tests/test_dataarray.py
@@ -1874,6 +1874,19 @@ class TestDataArray:
         bar = Variable([""x"", ""y""], np.zeros((10, 20)))
         assert_equal(self.dv, np.maximum(self.dv, bar))
 
+    def test_astype_attrs(self):
+        for v in [self.va.copy(), self.mda.copy(), self.ds.copy()]:
+            v.attrs[""foo""] = ""bar""
+            assert list(v.attrs.items()) == list(v.astype(float).attrs.items())
+            assert [] == list(v.astype(float, keep_attrs=False).attrs.items())
+
+    def test_astype_dtype(self):
+        original = DataArray([-1, 1, 2, 3, 1000])
+        converted = original.astype(float)
+        assert_array_equal(original, converted)
+        assert np.issubdtype(original.dtype, np.integer)
+        assert np.issubdtype(converted.dtype, np.floating)
+
     def test_is_null(self):
         x = np.random.RandomState(42).randn(5, 6)
         x[x < 0] = np.nan
diff --git a/xarray/tests/test_dataset.py b/xarray/tests/test_dataset.py
index da7621dc..9a95eb24 100644
--- a/xarray/tests/test_dataset.py
+++ b/xarray/tests/test_dataset.py
@@ -5607,6 +5607,17 @@ class TestDataset:
         np.testing.assert_equal(padded[""var1""].isel(dim2=[0, -1]).data, 42)
         np.testing.assert_equal(padded[""dim2""][[0, -1]].data, np.nan)
 
+    def test_astype_attrs(self):
+        data = create_test_data(seed=123)
+        data.attrs[""foo""] = ""bar""
+
+        assert list(data.attrs.items()) == list(data.astype(float).attrs.items())
+        assert list(data.var1.attrs.items()) == list(
+            data.astype(float).var1.attrs.items()
+        )
+        assert [] == list(data.astype(float, keep_attrs=False).attrs.items())
+        assert [] == list(data.astype(float, keep_attrs=False).var1.attrs.items())
+
 
 # Py.test tests
 
```
</details>","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-673678246,https://api.github.com/repos/pydata/xarray/issues/4314,673678246,MDEyOklzc3VlQ29tbWVudDY3MzY3ODI0Ng==,10194086,2020-08-13T19:52:26Z,2020-08-13T19:52:26Z,MEMBER,Weird - it got even worse. I can try tomorrow morning (European time) unless @max-sixty wants to have a go. ,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-673640237,https://api.github.com/repos/pydata/xarray/issues/4314,673640237,MDEyOklzc3VlQ29tbWVudDY3MzY0MDIzNw==,13837821,2020-08-13T18:29:48Z,2020-08-13T18:29:48Z,CONTRIBUTOR,"Did a fetch and rebase, not sure why commits from other PRs added to master in the meantime show up in this one 🤷 ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-673531471,https://api.github.com/repos/pydata/xarray/issues/4314,673531471,MDEyOklzc3VlQ29tbWVudDY3MzUzMTQ3MQ==,10194086,2020-08-13T15:02:55Z,2020-08-13T15:02:55Z,MEMBER,Somehow the  contents of #4248 got in here. Can you try to merge master and see if they disappear?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-672295017,https://api.github.com/repos/pydata/xarray/issues/4314,672295017,MDEyOklzc3VlQ29tbWVudDY3MjI5NTAxNw==,5635139,2020-08-11T21:45:01Z,2020-08-11T21:45:01Z,MEMBER,Great — I think this looks good — any final thoughts?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-672254759,https://api.github.com/repos/pydata/xarray/issues/4314,672254759,MDEyOklzc3VlQ29tbWVudDY3MjI1NDc1OQ==,14808389,2020-08-11T20:11:51Z,2020-08-11T20:11:51Z,MEMBER,"I think that's a false positive, our `flake8` and `black` CI don't report that. I guess the bot will remove that `FileNotFoundError` report once you push a new commit, so it should be safe to ignore it.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-672129254,https://api.github.com/repos/pydata/xarray/issues/4314,672129254,MDEyOklzc3VlQ29tbWVudDY3MjEyOTI1NA==,13837821,2020-08-11T17:46:30Z,2020-08-11T17:46:30Z,CONTRIBUTOR,I think(?) the pep warnings are from the commits @max-sixty pushed several days ago during testing,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-670769708,https://api.github.com/repos/pydata/xarray/issues/4314,670769708,MDEyOklzc3VlQ29tbWVudDY3MDc2OTcwOA==,13837821,2020-08-07T22:32:10Z,2020-08-07T22:32:10Z,CONTRIBUTOR,"Maybe I am overcomplicating things but I came up with this solution:

Catch the error. If it is the unallowed casting kwarg error, and we are dealing with a sparse array, pop the casting kwarg and issue a RuntimeWarning that we are doing so. Otherwise, raise the original error since it might be something else non-sparse related.

Does that seem reasonable?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-670248276,https://api.github.com/repos/pydata/xarray/issues/4314,670248276,MDEyOklzc3VlQ29tbWVudDY3MDI0ODI3Ng==,5635139,2020-08-06T23:59:16Z,2020-08-06T23:59:16Z,MEMBER,"I'm fine with reraising — though I think we should reraise, otherwise isn't it a confusing message?

The try-expect is probably fine given the narrowness (very open to holding too low a standard tho); one step up would be checking it is a spare array.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-670197090,https://api.github.com/repos/pydata/xarray/issues/4314,670197090,MDEyOklzc3VlQ29tbWVudDY3MDE5NzA5MA==,13837821,2020-08-06T21:18:40Z,2020-08-06T21:18:40Z,CONTRIBUTOR,"My solution of try/except and popping casting from kwargs felt a bit kludgey, so I'm definitely open to other ideas. Letting it raise and xfailing the test would mean that we can no longer perform `astype` on sparse arrays until a new sparse version is released in the future. Though I suppose that would depends on the next xarray vs sparse release timeline.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-670193537,https://api.github.com/repos/pydata/xarray/issues/4314,670193537,MDEyOklzc3VlQ29tbWVudDY3MDE5MzUzNw==,2448579,2020-08-06T21:09:56Z,2020-08-06T21:09:56Z,MEMBER,"I wonder if we should just let it raise (but xfail our test on sparse < 0.10.0). This is an ""imperfect NEP-18 implementation"" issue and it isn't feasible to catch all such errors.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-670157140,https://api.github.com/repos/pydata/xarray/issues/4314,670157140,MDEyOklzc3VlQ29tbWVudDY3MDE1NzE0MA==,5635139,2020-08-06T19:46:25Z,2020-08-06T19:46:25Z,MEMBER,"For sure — good idea to defer to numpy rather than raise — should we do that only on existing versions though? Otherwise we won't roll over to the new version when they do release their next version?
(the version check can be a single line, there are lots of examples in the repo, lmk if that's not clear)","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-670148385,https://api.github.com/repos/pydata/xarray/issues/4314,670148385,MDEyOklzc3VlQ29tbWVudDY3MDE0ODM4NQ==,13837821,2020-08-06T19:26:48Z,2020-08-06T19:26:48Z,CONTRIBUTOR,"Nice! Thanks a million @dcherian for raising that issue over at sparse. 

@max-sixty regarding the minimum version, it seems like sparse has a relatively infrequent release cycle (many months) so it could be a while before we have a minimum version to require. Could we check whether we are dealing with a sparse array and call the numpy method instead for that use case, until sparse supports it?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-670095439,https://api.github.com/repos/pydata/xarray/issues/4314,670095439,MDEyOklzc3VlQ29tbWVudDY3MDA5NTQzOQ==,5635139,2020-08-06T18:18:27Z,2020-08-06T18:18:27Z,MEMBER,What do you think about reraising the error with a message about upgrading? Is this a narrow enough use case that we can avoid backward-compat fix in xarray?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-670058108,https://api.github.com/repos/pydata/xarray/issues/4314,670058108,MDEyOklzc3VlQ29tbWVudDY3MDA1ODEwOA==,2448579,2020-08-06T17:08:19Z,2020-08-06T17:08:19Z,MEMBER,well that was fixed quickly! Now we need to think of backcompat workarounds.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-670019223,https://api.github.com/repos/pydata/xarray/issues/4314,670019223,MDEyOklzc3VlQ29tbWVudDY3MDAxOTIyMw==,2448579,2020-08-06T16:00:59Z,2020-08-06T16:00:59Z,MEMBER,I've opened an issue at sparse. Let's see what the outcome is.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-670014505,https://api.github.com/repos/pydata/xarray/issues/4314,670014505,MDEyOklzc3VlQ29tbWVudDY3MDAxNDUwNQ==,2448579,2020-08-06T15:53:10Z,2020-08-06T15:53:10Z,MEMBER,Looks like `COO.astype` doesn't accept the `casting` kwarg: https://sparse.pydata.org/en/stable/generated/sparse.COO.astype.html,"{""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-669610153,https://api.github.com/repos/pydata/xarray/issues/4314,669610153,MDEyOklzc3VlQ29tbWVudDY2OTYxMDE1Mw==,5635139,2020-08-06T00:16:33Z,2020-08-06T00:16:33Z,MEMBER,"I'm not sure re the test at first glance, I don't see how those tests are related, but master seems to pass. 
I pushed a merge to master as a check — hope that's OK. Let's see if that sheds any light","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961
https://github.com/pydata/xarray/pull/4314#issuecomment-669599057,https://api.github.com/repos/pydata/xarray/issues/4314,669599057,MDEyOklzc3VlQ29tbWVudDY2OTU5OTA1Nw==,13837821,2020-08-05T23:37:07Z,2020-08-05T23:37:07Z,CONTRIBUTOR,"Thanks @max-sixty. I pushed a second commit, including adding a `keep_attrs` argument so people can keep the old behavior of losing the attrs. I added a bit more testing on for general `astype` behavior, checking `dtype`s are correct and values are similar. 

What do you make of the failing tests in `test_sparse.py` (`test_dataarray_method` and `test_variable_method`)? I'm not really familiar enough with the pytest parametrize syntax to figure out what's going on.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,673757961